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.

Practice

1. What is the very first step to start using AWS cloud services?

easy

A. Write code to launch an AWS server

B. Call AWS support to request access

C. Download AWS software on your computer

D. Create an AWS account by signing up on the AWS website

Solution

1. Step 1: Understand AWS service access requirements

   To use AWS services, you must have an AWS account first.

2. Step 2: Identify how to create an AWS account

   AWS accounts are created by signing up on the AWS website, not by coding or calling support.

3. Final Answer:

   Create an AWS account by signing up on the AWS website -> Option D

4. Quick Check:

   First step to use AWS = Create account [OK]

Hint: AWS use starts with account signup on website [OK]

Common Mistakes:

• Thinking you can create an AWS account by code
• Assuming AWS software must be downloaded first
• Believing calling support is required to start

2. Which of the following is a required step during AWS account creation?

easy

A. Entering your email address and verifying it

B. Installing AWS CLI on your computer

C. Writing a CloudFormation template

D. Configuring an EC2 instance

Solution

1. Step 1: Identify required information for AWS signup

   AWS requires an email address to create an account and sends a verification email.

2. Step 2: Recognize unrelated steps

   Installing CLI, writing templates, or configuring instances happen after account creation.

3. Final Answer:

   Entering your email address and verifying it -> Option A

4. Quick Check:

   Email verification is mandatory during signup [OK]

Hint: Email verification is mandatory for AWS signup [OK]

Common Mistakes:

• Confusing account creation with later setup steps
• Thinking software installation is part of signup
• Assuming infrastructure setup is needed to create account

3. After successfully creating an AWS account, what is the immediate next step you must complete before using AWS services?

medium

A. Verify your phone number via SMS or call

B. Launch an EC2 instance

C. Create an IAM user

D. Write a billing report

Solution

1. Step 1: Recall AWS signup verification steps

   After account creation, AWS requires phone verification to confirm identity.

2. Step 2: Differentiate from other tasks

   Launching servers, creating users, or billing reports come after verification.

3. Final Answer:

   Verify your phone number via SMS or call -> Option A

4. Quick Check:

   Phone verification follows account creation [OK]

Hint: Phone verification is next after signup [OK]

Common Mistakes:

• Skipping phone verification step
• Trying to launch services before verification
• Confusing IAM user creation with signup process

4. You tried to create an AWS account but did not provide valid payment details. What will happen?

medium

A. You can use all AWS services without restrictions

B. Account creation will fail or be limited until payment info is added

C. AWS will automatically bill your phone number

D. You will be charged a fixed fee immediately

Solution

1. Step 1: Understand AWS payment requirements

   AWS requires valid payment info to activate the account fully and avoid service limits.

2. Step 2: Identify consequences of missing payment info

   Without payment details, account creation may fail or have restricted access.

3. Final Answer:

   Account creation will fail or be limited until payment info is added -> Option B

4. Quick Check:

   Valid payment info is required for full AWS account use [OK]

Hint: Payment info is mandatory for full AWS account activation [OK]

Common Mistakes:

• Assuming AWS services are free without payment info
• Thinking AWS bills phone numbers automatically
• Believing AWS charges fixed fees immediately

5. You want to create an AWS account for your small business. Which combination of steps is correct to complete the signup process successfully?

hard

A. Write CloudFormation template, verify email, call support, enter payment

B. Download AWS SDK, create IAM user, launch EC2, configure billing

C. Provide email, verify phone, enter payment details, accept terms

D. Create S3 bucket, verify phone, enter payment, accept terms

Solution

1. Step 1: List required signup steps

   Creating an AWS account requires email, phone verification, payment info, and agreeing to terms.

2. Step 2: Eliminate unrelated or incorrect steps

   Downloading SDK, creating resources, or calling support are not part of signup.

3. Final Answer:

   Provide email, verify phone, enter payment details, accept terms -> Option C

4. Quick Check:

   Signup = email + phone + payment + terms [OK]

Hint: Signup needs email, phone, payment, and terms acceptance [OK]

Common Mistakes:

• Confusing signup with resource setup
• Skipping terms acceptance
• Including unrelated steps like SDK download