Examkin

Question

Difficulty: MediumBilling, Cost Management, and Resource Sharing Strategy

A company has an AWS Organization consisting of a management account and multiple member accounts representing distinct business units: Network, Finance, and Engineering. The company wants to implement a resource sharing and cost management strategy that satisfies the following requirements:

- The Engineering unit must deploy its application workloads into a shared VPC hosted and managed by the Network account, while maintaining control over their own application-level security groups.
- The Finance unit requires internal showback reports where their Amazon EC2 usage has a 5%5\% markup applied, without affecting the actual consolidated invoice from AWS.

Which of the following actions should the solutions architect take to meet these requirements? (Select TWO.)

  1. Enable resource sharing within AWS Organizations from the management account. Use AWS Resource Access Manager (RAM) in the centralized Network account to share private subnets with the Engineering unit's accounts.Answer
  2. Configure AWS Billing Conductor in the billing management account. Create a billing group for the Finance unit's accounts, establish a custom pricing rule with a 5%5\% markup on Amazon EC2, and apply this rule to the billing group.Answer
  3. C
    Use AWS Resource Access Manager (RAM) in the Network account to share both the subnets and the security groups with the Engineering unit's accounts, allowing them to use centralized security groups.
  4. D
    In the centralized Network account, share the AWS-managed KMS key (aws/s3) with the Engineering unit's accounts to allow encryption of shared files in S3 buckets.
  5. E
    Apply a Service Control Policy (SCP) to the Finance unit's Organizational Unit (OU) to automatically apply a 5%5\% markup to the cost visualization in their Billing and Cost Management console.

Answer

Enable resource sharing within AWS Organizations and share the private subnets from the Network account via AWS RAM, and use AWS Billing Conductor to configure a custom billing group and pricing rule with a 5%5\% markup on Amazon EC2 for the Finance unit's accounts.
The correct strategy combines sharing VPC subnets using AWS Resource Access Manager (RAM) and configuring custom billing parameters using AWS Billing Conductor. Sharing subnets allows the Engineering account to deploy workloads into the central VPC and manage its own security groups, as security groups are not shared. AWS Billing Conductor enables the creation of pro forma billing data with custom markup or discount rules for specific accounts, fulfilling the Finance unit's requirement for showback without altering the master consolidated bill.

Step-by-Step Solution

1
Configure VPC sharing using AWS Resource Access Manager (RAM) in the Network account.
The subnets of the VPC are shared with the Engineering unit's AWS accounts within the Organization.
This allows the Engineering unit to launch resources into the shared subnet while maintaining control over their local security groups.
2
Configure AWS Billing Conductor in the management account.
A billing group is created containing the Finance unit's accounts, and a pricing rule applying a 5%5\% markup to EC2 is associated with this group.
This generates a custom billing view and pro forma invoice reflecting the markup for internal showback without changing the actual AWS billing data.

Key Concept

Implementing cross-account resource sharing using AWS Resource Access Manager (RAM) and custom billing reporting using AWS Billing Conductor.
Rate this question

Topics

Billing, Cost Management, and Resource Sharing Strategy

More questions from this topic