A company is using an organization in AWS Organizations to manage its multi-account AWS environment. A SysOps administrator needs to share a new Amazon Machine Image (AMI) with the entire…

Question

Options

• AMake the AMI public. Reference the AMI ID from within the member accounts of the organization.
• BShare the AMI's associated snapshots with all the accounts in the organization.
• CShare the AMI with the organization by specifying the organization Amazon Resource Name
• DUpload the AMI to AWS Marketplace. Search for the uploaded AMI when an instance is launched

• A
  10% (3)
• B
  7% (2)
• C
  79% (23)
• D
  3% (1)

Explanation

Sharing an AMI directly with the organization by specifying its ARN (e.g., arn:aws:organizations::123456789012:organization/o-xxxx) is the most operationally efficient method because it grants access to all current and future member accounts in a single action - no manual updates needed as accounts are added or removed.

Why the distractors are wrong:

• A - Making an AMI public exposes it to everyone on AWS, not just your organization; this is a security risk and fails the "organization-only" requirement.
• B - Sharing only the snapshots doesn't share the AMI itself, and it still requires manually specifying each account or repeating the action across accounts.
• D - Publishing to AWS Marketplace is a complex, multi-step process designed for commercial distribution, not internal account sharing - the opposite of operationally efficient.

Memory tip: Think of the org ARN as a "master key" - one share covers all accounts, past and present. Whenever an exam question asks about sharing resources across an entire organization with minimal ongoing effort, look for the answer that uses the organization ARN or organization ID as the target.

No community discussion yet for this question.