Amazon Machine Images (AMIs) in AWS - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

What happens when you deregister an AMI?

You have an AMI registered in your AWS account. You decide to deregister it. What is the immediate effect on instances launched from this AMI?

A Existing instances launched from the AMI continue running normally, but you cannot launch new instances from it.

B All existing instances launched from the AMI are terminated immediately.

C The AMI is deleted and all snapshots associated with it are also deleted immediately.

D You can still launch new instances from the AMI for 24 hours after deregistration.

💡 Hint

Think about what deregistering an AMI means for existing and new instances.

Deregistering an AMI prevents new instances from being launched using that AMI. However, existing instances continue to run unaffected because they are already launched.

❓ Architecture

intermediate

Choosing AMI for a multi-region deployment

You want to deploy an application in two AWS regions. You have a custom AMI in region A. What is the best way to use this AMI in region B?

A Launch instances in region B using the AMI ID from region A directly.

B Create a new AMI in region B by launching an instance and creating an AMI from it.

C Copy the AMI from region A to region B before launching instances.

D Use the public AMI with the same name in region B.

💡 Hint

AMIs are region-specific. Think about how to make an AMI available in another region.

AMIs are specific to a region. To use a custom AMI in another region, you must copy it to that region first. You cannot launch instances in one region using an AMI ID from another region.

❓ security

advanced

Securing AMI sharing with other AWS accounts

You want to share a private AMI with another AWS account securely. Which option ensures the AMI is shared but the underlying snapshots remain private?

A Export the AMI and send it as a file to the other account.

B Modify the AMI launch permissions to include the other account, but do not modify snapshot permissions.

C Create a public AMI so anyone can launch instances from it.

D Share the AMI and also share the snapshots with the other account explicitly.

💡 Hint

Think about what resources are needed to launch an instance from a shared AMI.

Sharing an AMI requires sharing both the AMI launch permissions and the underlying snapshots. Without snapshot permissions, the other account cannot launch instances from the AMI.

✅ Best Practice

advanced

Automating AMI creation with minimal downtime

You want to automate creating updated AMIs of your application servers daily with minimal downtime. Which approach is best?

A Manually create AMIs from instances during off-hours.

B Use AWS Systems Manager Automation to create AMIs from running instances without stopping them.

C Create AMIs only from stopped instances to ensure data consistency.

D Stop the instance, create an AMI, then start the instance again every day.

💡 Hint

Consider how to create AMIs without stopping instances to avoid downtime.

AWS Systems Manager Automation can create AMIs from running instances using snapshots, minimizing downtime. Stopping instances daily causes downtime and is less efficient.

🧠 Conceptual

expert

Understanding AMI lifecycle and snapshot dependencies

You deregister an AMI but keep its snapshots. Later, you create a new AMI using those snapshots. What is the impact on instance launch and storage costs?

A You can launch instances from the new AMI, and storage costs continue for snapshots until deleted.

B You cannot launch instances from the new AMI because snapshots are orphaned.

C Instances launched from the new AMI will be free of storage costs for snapshots.

D Storage costs stop immediately after deregistering the original AMI.

💡 Hint

Think about how snapshots relate to AMIs and billing.

Deregistering an AMI does not delete snapshots. You can create new AMIs from existing snapshots. Storage costs for snapshots continue until snapshots are deleted.