Creating an AWS account - Practice Exercises

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding AWS Account Creation Requirements

Which of the following is required to create a new AWS account?

A A government-issued ID document uploaded during signup

B A phone number from any country, even if not reachable

C A credit card issued only in the United States

D A valid email address that is not already associated with another AWS account

💡 Hint

Think about what AWS needs to uniquely identify your account and send notifications.

A valid email address is mandatory to create an AWS account because it serves as the unique identifier and contact point. Phone number must be reachable for verification but can be from many countries. Credit card is required but not limited to US-issued cards. Uploading government ID is not required during account creation.

❓ security

intermediate

Securing Your AWS Root Account

After creating an AWS account, what is the best practice to secure the root user?

A Enable multi-factor authentication (MFA) on the root user

B Share root user credentials with your team for easy access

C Use the root user for all daily tasks to avoid permission issues

D Disable the root user permanently

💡 Hint

Think about adding an extra layer of protection to the most powerful account.

Enabling MFA on the root user adds a second verification step, greatly improving security. Sharing root credentials or using root for daily tasks increases risk. The root user cannot be disabled but should be used sparingly.

❓ Architecture

advanced

Choosing the Right AWS Account Structure for a Growing Company

Your company plans to expand rapidly and wants to separate billing and permissions for different teams. Which AWS account strategy is most suitable?

A Create multiple AWS accounts but manage billing separately outside AWS

B Use a single AWS account and create IAM users for each team

C Create multiple AWS accounts and manage them under AWS Organizations

D Use one AWS account and share root credentials among teams

💡 Hint

Think about how AWS helps manage multiple accounts centrally.

AWS Organizations allows centralized management of multiple accounts, enabling separate billing and permissions per team. Using a single account with IAM users limits billing separation. Managing billing outside AWS is complex and error-prone. Sharing root credentials is insecure.

❓ service_behavior

advanced

AWS Account Activation Timing

After submitting your information to create a new AWS account, how long does it typically take before you can start using AWS services?

A Within a few minutes after email verification and payment method validation

B Immediately after submitting the signup form, no waiting required

C Only after receiving a physical welcome package by mail

D At least 24 hours due to manual review of account details

💡 Hint

Consider the automated checks AWS performs during signup.

AWS typically activates accounts within minutes after verifying your email and payment method. Immediate access without verification is not allowed. Manual reviews or physical mail are not standard parts of the process.

✅ Best Practice

expert

Managing Billing Alerts for a New AWS Account

You want to ensure your new AWS account does not exceed a monthly budget. Which approach best implements this using AWS native tools?

A Manually check the billing dashboard weekly for usage updates

B Set up AWS Budgets with email notifications and link it to your billing account

C Create an IAM policy that blocks resource creation after a budget limit is reached

D Use AWS CloudTrail to monitor billing events and send alerts

💡 Hint

Think about automated budget tracking and alerting features AWS provides.

AWS Budgets allows you to set spending thresholds and receive email alerts automatically. Manually checking is error-prone. IAM policies cannot enforce budget limits. CloudTrail logs API calls but does not track billing usage directly.