AWS Certified Solutions Architect – Professional — Question 293

An enterprise company is using a multi-account AWS strategy. There are separate accounts for development staging and production workloads. To control costs and improve governance the following requirements have been defined:
✑ The company must be able to calculate the AWS costs for each project.
✑ The company must be able to calculate the AWS costs for each environment development staging and production.
✑ Commonly deployed IT services must be centrally managed.
✑ Business units can deploy pre-approved IT services only.
✑ Usage of AWS resources in the development account must be limited.
Which combination of actions should be taken to meet these requirements? (Choose three.)

Answer options

• A. Apply environment, cost center, and application name tags to all taggable resources.
• B. Configure custom budgets and define thresholds using Cost Explorer.
• C. Configure AWS Trusted Advisor to obtain weekly emails with cost-saving estimates.
• D. Create a portfolio for each business unit and add products to the portfolios using AWS CloudFormation in AWS Service Catalog.
• E. Configure a billing alarm in Amazon CloudWatch.
• F. Configure SCPs in AWS Organizations to allow services available using AWS.

Correct answer: A, D, F

Explanation

Tagging resources with environment, cost center, and application details (Option A) enables granular cost tracking per project and environment. Utilizing AWS Service Catalog with AWS CloudFormation templates (Option D) ensures central management of IT services and restricts deployment to pre-approved products. Finally, implementing Service Control Policies (SCPs) via AWS Organizations (Option F) allows the organization to restrict resource usage in the development account, whereas options like CloudWatch billing alarms or Trusted Advisor do not enforce governance constraints.