Examkin

Question

Difficulty: MediumBilling, Cost Management, and Resource Sharing Strategy

A multinational retailer operates its workloads across multiple AWS accounts managed through AWS Organizations. To enforce consistent networking standards, the cloud engineering team needs to share a central Customer-Managed Prefix List containing verified on-premises data center ranges with all existing and future member accounts. Concurrently, the finance department wants to implement a cost-saving model for their compute usage. The workloads run on a mixture of Amazon EC2, AWS Fargate, and AWS Lambda. The solution must minimize administrative overhead and avoid manual resource acceptance steps.

Which strategy should a solutions architect propose to meet these requirements?

  1. Enable resource sharing with AWS Organizations in AWS RAM. Create a resource share for the prefix list in the sharing account and target the Organization's ID as the principal. From the management account, commit to Compute Savings Plans.Answer
  2. B
    Enable resource sharing with AWS Organizations in AWS RAM. Create a resource share for the prefix list in the sharing account and target the Organization's ID as the principal. From the management account, commit to EC2 Instance Savings Plans to cover the EC2, Fargate, and Lambda workloads.
  3. C
    Do not enable organization-wide sharing in AWS RAM. Create a resource share for the prefix list in the sharing account and target the Organization's ID. Attach a Service Control Policy (SCP) to the organization root that allows member accounts to bypass individual share acceptance. From the management account, commit to Compute Savings Plans.
  4. D
    Create a resource share for the prefix list in the sharing account and target the individual AWS account IDs of all member accounts. Have each member account manually accept the share invitation. From the management account, commit to EC2 Instance Savings Plans.

Answer

Enable resource sharing with AWS Organizations in AWS RAM, create a resource share targeting the Organization's ID, and purchase Compute Savings Plans from the management account.
Enabling resource sharing with AWS Organizations in AWS RAM allows resources to be shared seamlessly with the entire organization or specific OUs without requiring manual invitation acceptance. Since the workloads consist of Amazon EC2, AWS Fargate, and AWS Lambda, Compute Savings Plans are the most appropriate choice because they automatically apply to compute usage across all three services, regardless of instance family, size, or region.

Step-by-Step Solution

1
Configure AWS RAM to enable resource sharing within AWS Organizations.
Enables seamless sharing across accounts within the organization without requiring individual handshake invitation acceptances.
To minimize administrative overhead as required by the organization.
2
Create a resource share for the customer-managed prefix list and assign the Organization ID as the principal.
The prefix list becomes instantly available to all member accounts in the organization.
To distribute the authorized corporate IP ranges to all existing and future member accounts.
3
Acquire Compute Savings Plans in the management account.
Cost savings are automatically applied to eligible EC2, Fargate, and Lambda usage across all consolidated member accounts.
To cover the diverse compute workloads (EC2, Fargate, and Lambda) with maximum flexibility.

Key Concept

AWS Resource Access Manager sharing configurations within AWS Organizations and matching Savings Plans types to compute services (EC2, Fargate, Lambda) for multi-account cost optimization.
Rate this question

Topics

Billing, Cost Management, and Resource Sharing Strategy

More questions from this topic