AWS PowerShell module - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

Understanding AWS PowerShell Module Cmdlet Behavior

What will be the output of the following PowerShell command using AWS Tools for PowerShell?

Get-EC2Instance -InstanceIds 'i-1234567890abcdef0' | Select-Object -ExpandProperty Instances | Select-Object InstanceId, State

PowerShell

Get-EC2Instance -InstanceIds 'i-1234567890abcdef0' | Select-Object -ExpandProperty Instances | Select-Object InstanceId, State

A A list of objects showing InstanceId and State properties for the specified instance.

B An error indicating that 'Instances' property does not exist on the output object.

C No output because the command silently fails due to missing credentials.

D A list of all EC2 instances in the account ignoring the specified InstanceIds parameter.

💡 Hint

Consider what the -ExpandProperty parameter does in PowerShell and how AWS cmdlets return data.

The Get-EC2Instance cmdlet returns an object containing a property Instances which is a list of instance objects. Using -ExpandProperty Instances extracts that list so you can select properties like InstanceId and State directly.

❓ Configuration

intermediate

Configuring AWS Credentials in PowerShell

Which of the following commands correctly sets AWS credentials for the current PowerShell session using AWS Tools for PowerShell?

A Initialize-AWSDefaultConfiguration -AccessKey 'AKIA...' -SecretKey 'secret'

B Set-AWSDefaultCredential -AccessKey 'AKIA...' -SecretKey 'secret'

C Set-AWSCredential -AccessKey 'AKIA...' -SecretKey 'secret' -StoreAs 'MyProfile'

D New-AWSCredential -AccessKey 'AKIA...' -SecretKey 'secret' -ProfileName 'MyProfile'

💡 Hint

Look for the cmdlet that explicitly sets credentials and optionally stores them under a profile name.

Set-AWSCredential is the correct cmdlet to set AWS credentials in the current session and optionally save them under a profile name for reuse.

❓ Architecture

advanced

Designing a PowerShell Script for AWS Resource Cleanup

You want to write a PowerShell script using AWS Tools for PowerShell to delete all EC2 instances with a specific tag key-value pair. Which approach below correctly lists and deletes only those instances?

A Use <code>Get-EC2Instance</code> with <code>-Filter @{Name='tag:Key'; Values='Value'}</code> to get instances, then pipe to <code>Remove-EC2Instance</code> with <code>-InstanceId</code> parameter.

B Use <code>Get-EC2Instance</code> without filters, then filter instances in PowerShell by tag, then call <code>Remove-EC2Instance</code> with instance IDs.

C Use <code>Get-EC2Instance</code> with <code>-InstanceIds</code> parameter set to tag values, then delete instances.

D Use <code>Remove-EC2Instance</code> with <code>-Filter @{Name='tag:Key'; Values='Value'}</code> directly to delete instances.

💡 Hint

Think about how AWS cmdlets accept filters and how deletion cmdlets require instance IDs.

Get-EC2Instance supports filtering by tags to list matching instances. Remove-EC2Instance requires instance IDs to delete. So first filter, then delete by IDs.

❓ security

advanced

Handling AWS Credentials Securely in PowerShell Scripts

Which practice below is the most secure way to handle AWS credentials in PowerShell scripts for automation?

A Prompt the user to enter credentials interactively every time the script runs.

B Hardcode AWS Access Key and Secret Key directly in the script variables.

C Store credentials in plain text files and read them in the script at runtime.

D Use IAM roles attached to the compute environment and avoid embedding credentials in scripts.

💡 Hint

Consider AWS best practices for credential management in automated environments.

Using IAM roles attached to the compute environment (like EC2 or Lambda) allows automatic, secure credential management without embedding secrets in scripts.

🧠 Conceptual

expert

Understanding AWS PowerShell Module Credential Resolution Order

In what order does the AWS Tools for PowerShell module resolve credentials when executing a cmdlet?

A IAM role &gt; Shared credentials file &gt; Environment variables &gt; Explicit credentials passed to the cmdlet

B Explicit credentials passed to the cmdlet &gt; Environment variables &gt; Shared credentials file &gt; IAM role

C Shared credentials file &gt; Explicit credentials passed to the cmdlet &gt; IAM role &gt; Environment variables

D Environment variables &gt; IAM role &gt; Explicit credentials passed to the cmdlet &gt; Shared credentials file

💡 Hint

Think about the precedence of credentials explicitly provided versus environment or role-based credentials.

The AWS Tools for PowerShell first use credentials explicitly passed to the cmdlet, then environment variables, then the shared credentials file (~/.aws/credentials), and finally IAM roles if running on AWS compute resources.

Practice

1. What is the primary purpose of the AWS PowerShell module?

easy

A. To replace the AWS Management Console entirely

B. To create Windows PowerShell scripts only for local tasks

C. To develop desktop applications for AWS

D. To manage AWS services using PowerShell commands

Solution

1. Step 1: Understand AWS PowerShell module purpose

   The module allows managing AWS services through PowerShell commands, enabling automation and scripting.

2. Step 2: Compare options with module purpose

   Only To manage AWS services using PowerShell commands correctly states this purpose; others describe unrelated or incorrect uses.

3. Final Answer:

   To manage AWS services using PowerShell commands -> Option D

4. Quick Check:

   AWS PowerShell module = Manage AWS with PowerShell [OK]

Hint: AWS PowerShell module = AWS service management via PowerShell [OK]

Common Mistakes:

• Thinking it only works locally without AWS connection
• Confusing it with AWS Management Console
• Assuming it builds desktop apps

2. Which command correctly imports the AWS PowerShell module in your session?

easy

A. Import-Module AWS.Tools.Common

B. Import-AWSModule

C. Load-Module AWS.Tools

D. Start-Module AWS.Tools.Common

Solution

1. Step 1: Identify correct PowerShell import syntax

   The correct command to import a module is Import-Module followed by the module name.

2. Step 2: Match AWS module import command

   Import-Module AWS.Tools.Common uses correct syntax and module name 'AWS.Tools.Common'. Other options use invalid cmdlets or incorrect names.

3. Final Answer:

   Import-Module AWS.Tools.Common -> Option A

4. Quick Check:

   Import-Module + module name = correct import [OK]

Hint: Use Import-Module with exact AWS module name [OK]

Common Mistakes:

• Using incorrect cmdlet names like Import-AWSModule
• Confusing Load-Module or Start-Module with Import-Module
• Misspelling module names

3. What will the following PowerShell command output if your AWS credentials are set correctly?

Get-STSCallerIdentity | Select-Object -ExpandProperty Account

medium

A. An error saying command not found

B. The AWS account ID associated with your credentials

C. The list of all AWS regions

D. The current IAM user name

Solution

1. Step 1: Understand Get-STSCallerIdentity cmdlet

   This cmdlet returns details about the AWS identity used, including the Account property.

2. Step 2: Analyze Select-Object usage

   Select-Object with -ExpandProperty Account extracts and outputs only the AWS account ID string.

3. Final Answer:

   The AWS account ID associated with your credentials -> Option B

4. Quick Check:

   Get-STSCallerIdentity + Account property = AWS account ID [OK]

Hint: Get-STSCallerIdentity shows your AWS account info [OK]

Common Mistakes:

• Expecting user name instead of account ID
• Thinking it lists regions
• Assuming command fails without credentials

4. You run this command but get an error: Get-S3Bucket is not recognized. What is the most likely cause?

medium

A. The S3 service is down

B. Your AWS credentials are incorrect

C. AWS PowerShell module is not imported

D. You need to restart PowerShell

Solution

1. Step 1: Understand error meaning

   Error 'command not recognized' means PowerShell does not know the cmdlet, usually because the module is not loaded.

2. Step 2: Check other causes

   Incorrect credentials or service downtime cause different errors; restarting PowerShell is rarely needed if module is imported.

3. Final Answer:

   AWS PowerShell module is not imported -> Option C

4. Quick Check:

   Cmdlet not recognized = module missing [OK]

Hint: Import AWS module before using its cmdlets [OK]

Common Mistakes:

• Blaming credentials for cmdlet not found error
• Assuming service downtime causes this error
• Restarting PowerShell unnecessarily

5. You want to list all EC2 instances in the 'us-east-1' region using AWS PowerShell. Which command correctly sets the region and retrieves the instances?

hard

A. Set-DefaultAWSRegion -Region us-east-1; Get-EC2Instance

B. Get-EC2Instance -RegionName us-east-1

C. Set-AWSRegion us-east-1; Get-EC2Instance

D. Get-EC2Instance | Where-Object { $_.Region -eq 'us-east-1' }

Solution

1. Step 1: Identify how to set AWS region in PowerShell

   The cmdlet to set default region is Set-DefaultAWSRegion with -Region parameter.

2. Step 2: Retrieve EC2 instances after setting region

   After setting region, Get-EC2Instance fetches instances in that region. Set-DefaultAWSRegion -Region us-east-1; Get-EC2Instance correctly chains these commands.

3. Step 3: Evaluate other options

   Get-EC2Instance -RegionName us-east-1 uses invalid parameter '-RegionName'; Set-AWSRegion us-east-1; Get-EC2Instance uses a non-existent cmdlet; Get-EC2Instance | Where-Object { $_.Region -eq 'us-east-1' } filters instances locally but region info is not a direct property.

4. Final Answer:

   Set-DefaultAWSRegion -Region us-east-1; Get-EC2Instance -> Option A

5. Quick Check:

   Set region first, then get instances [OK]

Hint: Set region with Set-DefaultAWSRegion before commands [OK]

Common Mistakes:

• Using wrong cmdlet to set region
• Passing -Region directly to Get-EC2Instance
• Filtering region locally without setting it