Why account management matters in AWS - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why separate AWS accounts for different teams?

Imagine a company with multiple teams using AWS. Why is it important to use separate AWS accounts for each team instead of sharing one account?

A Because AWS does not allow multiple users in the same account.

B To isolate billing and security boundaries, so teams don't affect each other's resources or costs.

C To reduce the number of AWS regions available to each team.

D Because each team needs a different AWS Management Console design.

💡 Hint

Think about how mistakes or costs in one team could impact others.

Using separate AWS accounts helps isolate billing and security. If one team makes a mistake or uses many resources, it won't affect other teams. It also helps with clear cost tracking and applying security policies per team.

❓ Architecture

intermediate

What is the best AWS account structure for a company with multiple environments?

A company has development, testing, and production environments. Which AWS account structure best supports clear separation and control?

A Use separate AWS accounts for development, testing, and production environments.

B Use one AWS account and separate environments by tags on resources.

C Use one AWS account and separate environments by different AWS regions.

D Use one AWS account and separate environments by different IAM users.

💡 Hint

Consider how to prevent accidental changes in production.

Using separate AWS accounts for each environment provides strong isolation. It prevents accidental access or changes across environments and simplifies applying environment-specific policies and billing.

❓ security

advanced

What risk arises from using a single AWS account for all projects?

What is a major security risk when all projects share one AWS account?

A Billing is separated per project, so costs are easy to track.

B AWS automatically blocks access to resources from different projects in the same account.

C A compromised credential can access all projects' resources without restriction.

D IAM roles cannot be created in a single AWS account.

💡 Hint

Think about what happens if one user's password is stolen.

In a single AWS account, if credentials are compromised, the attacker can access all resources in that account. This risk is reduced by separating projects into different accounts.

✅ Best Practice

advanced

How does AWS Organizations help with account management?

Which feature of AWS Organizations helps manage multiple AWS accounts efficiently?

A It allows centralized billing and applying policies across accounts.

B It merges all accounts into one to simplify management.

C It disables IAM roles in member accounts.

D It restricts access to only one AWS region per account.

💡 Hint

Think about managing many accounts from one place.

AWS Organizations lets you group accounts, consolidate billing, and apply security policies centrally. This simplifies managing multiple accounts securely and cost-effectively.

❓ service_behavior

expert

What happens if you delete the master account in AWS Organizations?

In AWS Organizations, what is the effect of deleting the master (management) account?

A The organization is deleted but member accounts continue independently.

B All member accounts are automatically deleted as well.

C The master account is converted to a member account automatically.

D You cannot delete the master account; it must remain to manage the organization.

💡 Hint

Consider the role of the master account in AWS Organizations.

The master account is the root of the AWS Organization and cannot be deleted. It is required to manage the organization and its member accounts.