Bird
0
0

Why might an AMI fail to launch an instance even if it exists and you have permissions?

hard📝 Conceptual Q10 of 15
AWS - EC2 Fundamentals
Why might an AMI fail to launch an instance even if it exists and you have permissions?
AThe AMI is shared publicly
BThe AMI's root device type is incompatible with the selected instance type
CThe AMI is encrypted
DThe AMI has no associated snapshots
Step-by-Step Solution
Solution:

  1. Step 1: Understand root device type compatibility

    Some instance types only support certain root device types (EBS or instance store). Incompatibility causes launch failure.

  2. Step 2: Exclude other options

    Encryption or public sharing does not prevent launch if permissions are correct; AMI always has snapshots.

  3. Final Answer:

    The AMI's root device type is incompatible with the selected instance type -> Option B

  4. Quick Check:

    Root device type mismatch blocks instance launch [OK]
Quick Trick: Match AMI root device type with instance type to launch [OK]
Common Mistakes:
  • Assuming encryption blocks launch
  • Confusing public sharing with launch failure
  • Ignoring root device compatibility

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More AWS Quizzes
AWS Account and Billing - Resource tagging for cost tracking - Quiz 11easy AWS Account and Billing - Why account management matters - Quiz 10hard Cloud Computing Fundamentals - AWS Management Console walkthrough - Quiz 8hard Cloud Computing Fundamentals - AWS Management Console walkthrough - Quiz 12easy Identity and Access Management - IAM users and groups - Quiz 3easy Identity and Access Management - IAM users and groups - Quiz 2easy Identity and Access Management - IAM best practices - Quiz 8hard S3 Fundamentals - Bucket policies for access control - Quiz 4medium S3 Fundamentals - Static website hosting on S3 - Quiz 3easy Security Groups and Network ACLs - Stateless behavior of NACLs - Quiz 7medium