Bird
0
0

Why does AWS charge for Elastic IP addresses that are allocated but not associated with a running instance?

hard📝 Conceptual Q10 of 15
AWS - EC2 Fundamentals
Why does AWS charge for Elastic IP addresses that are allocated but not associated with a running instance?
ATo encourage efficient use of scarce public IPv4 addresses
BBecause Elastic IPs consume instance CPU resources
CBecause unassociated Elastic IPs increase network traffic
DTo cover costs of DNS resolution for Elastic IPs
Step-by-Step Solution
Solution:

  1. Step 1: Understand AWS Elastic IP pricing rationale

    AWS charges to discourage hoarding of limited public IPv4 addresses.

  2. Step 2: Evaluate other options

    Elastic IPs do not consume CPU or increase traffic; DNS resolution is unrelated to Elastic IP charges.

  3. Final Answer:

    To encourage efficient use of scarce public IPv4 addresses -> Option A

  4. Quick Check:

    Charges prevent Elastic IP wastage [OK]
Quick Trick: AWS charges to prevent Elastic IP hoarding [OK]
Common Mistakes:
MISTAKES
  • Thinking charges relate to CPU or traffic
  • Assuming DNS costs cause charges
  • Not knowing IPv4 scarcity drives pricing

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More AWS Quizzes
AWS CLI - Installing AWS CLI - Quiz 7medium Cloud Computing Fundamentals - Why cloud over on-premises - Quiz 13medium Cloud Computing Fundamentals - AWS Management Console walkthrough - Quiz 12easy EC2 Fundamentals - Instance states (running, stopped, terminated) - Quiz 3easy EC2 Fundamentals - Instance types and families - Quiz 15hard EC2 Fundamentals - Key pairs for SSH access - Quiz 13medium Identity and Access Management - IAM best practices - Quiz 8hard S3 Fundamentals - Why S3 matters for object storage - Quiz 14medium Security Groups and Network ACLs - Stateful behavior of security groups - Quiz 8hard Security Groups and Network ACLs - Stateless behavior of NACLs - Quiz 6medium