Why account management matters in AWS - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a new AWS account using AWS Organizations.

AWS

response = client.create_account(AccountName=[1], Email='[e-mail]')

Drag options to blanks, or click blank then click option'

A'MyNewAccount'

BMyNewAccount

Caccount_name

D123456789012

Attempts:

3 left

💡 Hint

Common Mistakes

Forgetting to put quotes around the account name.

You must provide the account name as a string in quotes.

2fill in blank

medium

Complete the code to list all AWS accounts in your organization.

AWS

accounts = client.list_accounts()[1]

Drag options to blanks, or click blank then click option'

A.items()

B.Accounts

C['Accounts']

D.get('Accounts')

Attempts:

3 left

💡 Hint

Common Mistakes

Using dot notation instead of .get() for dictionary keys.

The list_accounts() method returns a dictionary. Use .get('Accounts') to access the accounts list.

3fill in blank

hard

Fix the error in the code to attach a policy to an AWS account.

AWS

client.attach_policy(PolicyId=[1], TargetId='123456789012')

Drag options to blanks, or click blank then click option'

A123456789012

Bpolicy_id

C'p-abcdefg123'

D'123456789012'

Attempts:

3 left

💡 Hint

Common Mistakes

Using an unquoted variable or number for PolicyId.

PolicyId must be a string with quotes, like 'p-abcdefg123'.

4fill in blank

hard

Fill both blanks to create a new organizational unit (OU) under a root.

AWS

response = client.create_organizational_unit(ParentId=[1], Name=[2])

Drag options to blanks, or click blank then click option'

A'r-examplerootid'

B'MyOU'

CMyOU

Dr-examplerootid

Attempts:

3 left

💡 Hint

Common Mistakes

Leaving out quotes around string parameters.

ParentId and Name must be strings with quotes.

5fill in blank

hard

Fill the blanks to tag an AWS account with a key and value.

AWS

client.tag_resource(ResourceId=[1], Tags=[[2]])

Drag options to blanks, or click blank then click option'

A'123456789012'

B{'Key': 'Environment', 'Value': 'Production'}

C{'Key': 'Owner', 'Value': 'TeamA'}

D'arn:aws:organizations::123456789012:account/o-exampleorgid/123456789012'

Attempts:

3 left

💡 Hint

Common Mistakes

Using ARN instead of account ID for ResourceId.

Not formatting Tags as a list of dicts.

ResourceId is the account ID as a string. Tags is a list of dictionaries with Key and Value.

Practice

1. Why is account management important in AWS cloud environments?

easy

A. It helps keep resources safe and organized.

B. It automatically fixes all security issues.

C. It makes cloud services free to use.

D. It removes the need for user permissions.

Solution

1. Step 1: Understand the role of account management

   Account management organizes cloud resources and controls who can access them.

2. Step 2: Identify the correct benefit

   Keeping resources safe and organized is a key benefit of account management.

3. Final Answer:

   It helps keep resources safe and organized. -> Option A

4. Quick Check:

   Account management = safety and organization [OK]

Hint: Account management = safety + organization [OK]

Common Mistakes:

• Thinking it fixes security automatically
• Believing cloud services become free
• Assuming no need for permissions

2. Which AWS service is used to manage multiple AWS accounts centrally?

easy

A. AWS Organizations

B. AWS IAM

C. Amazon S3

D. AWS Lambda

Solution

1. Step 1: Identify the service for account grouping

   AWS Organizations is designed to manage multiple AWS accounts centrally.

2. Step 2: Differentiate from other services

   AWS IAM manages users and permissions within an account, not multiple accounts.

3. Final Answer:

   AWS Organizations -> Option A

4. Quick Check:

   Multiple account management = AWS Organizations [OK]

Hint: Multiple accounts? Use AWS Organizations [OK]

Common Mistakes:

• Confusing IAM with account management
• Choosing unrelated services like S3 or Lambda
• Thinking IAM manages multiple accounts

3. Given this AWS IAM policy snippet, what does it allow?

{
  "Effect": "Allow",
  "Action": "s3:ListBucket",
  "Resource": "arn:aws:s3:::example-bucket"
}

medium

A. Allows listing objects inside example-bucket

B. Allows listing the example-bucket itself

C. Allows listing all buckets in the account

D. Allows deleting example-bucket

Solution

1. Step 1: Understand the Action and Resource

   The action 's3:ListBucket' allows listing the bucket itself, which includes metadata and the ability to list objects inside.

2. Step 2: Differentiate from other permissions

   This permission allows listing the bucket (its contents), but not listing all buckets (which requires s3:ListAllMyBuckets) or deleting.

3. Final Answer:

   Allows listing the example-bucket itself -> Option B

4. Quick Check:

   s3:ListBucket on bucket ARN = list bucket contents [OK]

Hint: s3:ListBucket on bucket = list bucket contents [OK]

Common Mistakes:

• Thinking it lists objects inside the bucket only
• Confusing with s3:ListAllMyBuckets for all buckets
• Assuming it allows deletion

4. You created an AWS Organization but users in member accounts cannot access shared resources. What is the likely issue?

medium

A. You forgot to enable consolidated billing

B. Member accounts are not linked to AWS IAM

C. AWS Organizations does not support resource sharing

D. You did not set proper IAM permissions for cross-account access

Solution

1. Step 1: Check AWS Organizations capabilities

   AWS Organizations supports resource sharing but requires permissions set correctly.

2. Step 2: Identify permission setup issue

   Without proper IAM permissions, users cannot access resources across accounts.

3. Final Answer:

   You did not set proper IAM permissions for cross-account access -> Option D

4. Quick Check:

   Cross-account access needs IAM permissions [OK]

Hint: Cross-account access needs IAM permissions [OK]

Common Mistakes:

• Assuming billing controls access
• Believing Organizations can't share resources
• Thinking member accounts lack IAM

5. You want to track costs separately for different teams using AWS accounts. What is the best practice to manage this?

hard

A. Use one AWS account and tag resources by team.

B. Share one AWS account login among all teams.

C. Create separate AWS accounts for each team under AWS Organizations.

D. Disable AWS Organizations and use IAM groups instead.

Solution

1. Step 1: Understand cost tracking needs

   Separate accounts allow clear cost separation and billing for each team.

2. Step 2: Compare with tagging and shared accounts

   Tagging helps but can be error-prone; sharing accounts mixes costs and risks security.

3. Step 3: Evaluate AWS Organizations role

   AWS Organizations lets you manage multiple accounts easily and consolidate billing.

4. Final Answer:

   Create separate AWS accounts for each team under AWS Organizations. -> Option C

5. Quick Check:

   Separate accounts = clear cost tracking [OK]

Hint: Separate accounts per team for clear cost tracking [OK]

Common Mistakes:

• Using one account with tags only
• Sharing login credentials
• Disabling Organizations for this purpose