Examkin

Question

Difficulty: HardBilling, Cost Management, and Resource Sharing Strategy

A global logistics enterprise has a multi-account structure managed under AWS Organizations with Consolidated Billing. The enterprise has three main OUs: Production, Development, and Shared Services. The enterprise has the following requirements:

1. Share subnets from a central VPC in the Shared Services account with the Production OU to enable direct network communication without VPC peering.
2. Purchase a Savings Plan to reduce costs for a mix of Amazon EC2, AWS Fargate, and AWS Lambda workloads running in the Production OU, while preventing these savings from being applied to the Development OU.
3. For a newly acquired subsidiary whose accounts are in a separate OU, the finance team requires a custom pro-forma billing view that applies a 5% markup on all AWS public rates.

Which two of the following options should the Solutions Architect implement to meet these requirements? (Select TWO.)

  1. Enable resource sharing within AWS Organizations. In the Shared Services account, create an AWS Resource Access Manager (RAM) resource share for the subnets and associate it with the Production OU. Purchase Compute Savings Plans in the Management account, and disable Savings Plans discount sharing for the Development OU in the Billing Preferences of the Management account.Answer
  2. In the Management account, use AWS Billing Conductor to create a billing group with the primary account of the subsidiary as the billing group owner. Create a pricing rule with a global markup of 5%, associate this pricing rule with the billing group, and configure the billing group to generate pro forma Cost and Usage Reports (CUR).Answer
  3. C
    Enable resource sharing within AWS Organizations. In the Shared Services account, share the subnets with the Production OU using AWS RAM. Purchase EC2 Instance Savings Plans in the Management account, and attach a Service Control Policy (SCP) to the Development OU that denies the 'savingsplans:Apply' action to restrict discount application.
  4. D
    In the Shared Services account, create a subnet resource share in AWS RAM. Enable external sharing in the RAM console and share the subnets with the individual AWS account IDs of the Production OU. Use a default AWS-managed KMS key ('aws/s3') in the Shared Services account to encrypt all cross-account flow logs, and delegate access to the Production OU by modifying the KMS key policy.
  5. E
    Create a billing group in AWS Billing Conductor for the subsidiary accounts. Attach an SCP to the subsidiary OU that denies access to the 'aws-portal:*' actions to enforce the 5% markup. Purchase Compute Savings Plans in the Shared Services account, and use AWS RAM to share the Savings Plan resource with the Production OU.

Answer

The Solutions Architect should enable resource sharing in AWS Organizations, share subnets via AWS RAM with the Production OU, purchase Compute Savings Plans in the Management account while disabling sharing for the Development OU under Billing Preferences, and use AWS Billing Conductor to configure a billing group with a 5% markup pricing rule for the subsidiary accounts.
The correct options involve sharing subnets using AWS RAM, purchasing Compute Savings Plans with selectively disabled sharing for the Development OU, and leveraging AWS Billing Conductor to define a custom billing group and markup rule. This configuration securely extends network sharing to the Production OU, optimizes cross-service compute costs without bleeding discounts into non-production accounts, and enforces the required custom billing rates for the subsidiary.

Step-by-Step Solution

1
Determine the resource sharing method and choose the appropriate Savings Plan type.
Subnets must be shared via AWS RAM under AWS Organizations. To cover EC2, Fargate, and Lambda workloads, a Compute Savings Plan must be selected.
AWS RAM supports subnet sharing within the organization. Only Compute Savings Plans cover all three required compute services (EC2, Fargate, and Lambda).
2
Address the constraint to prevent Savings Plan sharing with the Development OU.
Disable Savings Plan discount sharing for the Development OU in the Billing Preferences of the Management account.
AWS Organizations consolidated billing applies Savings Plans discounts to all accounts by default. Billing Preferences is the correct mechanism to selectively restrict discount application.
3
Configure the pro-forma billing and custom markup for the subsidiary.
Use AWS Billing Conductor to establish a billing group for the subsidiary accounts and define a pricing rule that applies a 5% markup.
AWS Billing Conductor is specifically designed to customize pricing parameters and generate pro forma reports for internal departments and subsidiaries.

Key Concept

Selective billing discount allocation, custom billing groups with markup pricing rules, and internal multi-account subnet sharing.
Rate this question

Topics

Billing, Cost Management, and Resource Sharing Strategy

More questions from this topic