You want another AWS account in your organization to launch instances from your private AMI. What is the standard approach?
A. Send them the instance’s private IP
B. Modify AMI launch permissions to allow the target account (or use AWS Organizations / RAM patterns as appropriate)
C. Change the Region of the AMI to match their default Region
D. Publicly post the AMI on the internet
b. modify ami launch permissions to allow the target or use aws organistation /ram patterns as appropriate
When copying an AMI to another Region, what is a key implication?
A. The destination Region gets a new AMI ID and new snapshot IDs
B. The source AMI is deleted automatically
C. The private IP addresses move with the AMI
D. Cross-Region copy always fails for encrypted AMIs
c. a. the destination region gets a new ami id and new snap shot id
Which factor does not typically determine whether you choose a particular AMI when launching an instance?
A. Processor architecture (e.g., x86_64 vs arm64)
B. Whether the AMI supports the instance type family you selected
C. The color of the EC2 console theme
D. Whether the AMI includes the OS and drivers you need
c. the color of the ec2 console theme
An AMI is often described as including launch permissions and what else?
A. Only IAM user passwords
B. A block device mapping that describes volumes to attach at launch
C. Automatic Application Load Balancer creation
D. Reserved Instance contracts
b. a block device mapping that describe volumes to attach at launch
After you deregister a custom AMI, what usually remains until you clean it up?
A. Nothing; everything is removed instantly with no further steps
B. Snapshots that backed the AMI may still exist and incur storage cost until deleted
C. The EC2 instances launched from that AMI are always terminated automatically
D. The AMI remains launchable for 30 days as a “soft delete” in all cases
b.snapshot that backed the ami may still exits and incur storage cost untill delated
Charger plus de questions