Examkin

Question

Difficulty: MediumBilling, Cost Management, and Resource Sharing Strategy

A technology cooperative is establishing a shared services platform across multiple AWS accounts within an AWS Organization. The cooperative wants to create a shared VPC in a central Infrastructure account to host application load balancers and share subnets with regional application accounts. Additionally, they plan to purchase a single Savings Plan from the billing management account that applies to Amazon EC2 and AWS Fargate usage across all member accounts. The cooperative also wants to ensure that any individual member account can be excluded from sharing the unused Savings Plans capacity if required. Which TWO actions should the solutions architect take to implement this strategy? (Select TWO.)

  1. From the central Infrastructure account, use AWS Resource Access Manager (RAM) to create a resource share for the specific VPC subnets, sharing them with the organizational units (OUs) that contain the regional application accounts.Answer
  2. Purchase Compute Savings Plans in the billing management account, and configure the discount sharing preferences in the management account's billing console to exclude specific member accounts that prefer not to share their discount capacity.Answer
  3. C
    Purchase EC2 Instance Savings Plans in the billing management account to maximize discounts across both the Amazon EC2 instances and AWS Fargate tasks running in the application OUs.
  4. D
    Share the entire VPC from the central Infrastructure account using AWS Resource Access Manager (RAM) with external sharing enabled, allowing regional accounts to provision resources directly into any unshared subnet within that VPC.
  5. E
    Attach a Service Control Policy (SCP) to the application OUs that explicitly allows the ram:AssociateResourceShare action to grant the application accounts permission to launch resources in the shared subnets without local IAM configurations.

Answer

The correct actions are to use AWS Resource Access Manager (RAM) to share the specific subnets from the Infrastructure account with the application OUs, and to purchase Compute Savings Plans in the management account while configuring discount sharing exclusions for specific member accounts in the billing console.
The correct architecture involves sharing subnets via AWS Resource Access Manager (RAM) to allow member accounts to deploy resources within a centralized VPC, and purchasing Compute Savings Plans in the management account while configuring discount sharing settings to exclude specific member accounts that wish to opt out.

Step-by-Step Solution

1
Select the correct resource sharing mechanism for multi-account networking.
Identify that subnets (not the entire VPC) must be shared via AWS Resource Access Manager (RAM) with the destination OUs.
AWS RAM supports sharing subnets, allowing resources in other accounts to be launched into the shared subnet while keeping VPC administration centralized.
2
Select the appropriate Savings Plan type to cover both EC2 and Fargate.
Determine that Compute Savings Plans must be purchased because they apply to both EC2 and Fargate, unlike EC2 Instance Savings Plans which only cover EC2.
Meeting the requirement to apply discounts to both compute types requires a plan that covers Fargate.
3
Configure discount sharing preferences in the management account.
Adjust the Billing Preferences in the management account to disable discount sharing for specific member accounts.
By default, Savings Plans benefits are shared across all accounts in the organization, but the management account can selectively disable sharing for specific accounts.

Key Concept

AWS RAM Subnet Sharing and Savings Plans Discount Customization in Multi-Account Organizations
Estimated Time:2m 0s
Rate this question

Topics

Billing, Cost Management, and Resource Sharing Strategy

More questions from this topic