Q1 — AWS SAA-C03 Ch.15
Question 1 of 100 | ← Chapter 15
Q1101. An application team uses an organization in AWS Organizations to manage multiple AWS accounts in a dedicated Organizational Unit (OU). The accounts do not host production workloads. The application team exceeds its budget every month. A solutions architect needs to implement controls to prevent the application team from exceeding the team's budget.Which solution will meet this requirement?
- A. Create a usage report in AWS Cost Explorer.Set up automated alerts to notify the application team when usage exceeds the budget so the team can take immediate actions to reduce costs.
- B. Create a fixed monthly budget in AWS Budgets. Create a budget action to apply a service control policy (SCP) to the OU to deny additional usage when the team reaches the monthly budget. ✓
- C. Create an Amazon CloudWatch metric and a ClourWatch alarm for the application team's usage.Configure an AWS Lambda to use predefined tags to identify and stop nonessential services.
- D. Use AWS Cost Anomaly Detection to monitor the application team's usage and to alert the application team about unexpected spending patterns.
Correct Answer: B. Create a fixed monthly budget in AWS Budgets. Create a budget action to apply a service control policy (SCP) to the OU to deny additional usage when the team reaches the monthly budget.
Explanation
To address the requirement of implementing controls to prevent the application team from exceeding their budget in AWS Organizations, we need to consider solutions that provide automated enforcement of budget limits. Let's evaluate each option:A. Create a usage report in AWS Cost Explorer. Set up automated alerts to notify the application team when usage exceeds the budget so the team can take immediate actions to reduce costs.This option provides visibility into cost and usage patterns and allows for setting up alerts. However, it relies on manual intervention by the application team to take corrective actions once an alert is triggered.It does not enforce a budget limit automatically.B. Create a fixed monthly budget in AWS Budgets. Create a budget action to apply a service control policy (SCP) to the OU to deny additional usage when the team reaches the monthly budget.This option uses AWS Budgets to set a fixed monthly budget. By creating a budget action that applies an SCP to the OU, it automatically enforces the budget limit. Once the budget is reached, the SCP will deny additional usage, effectively preventing the team from exceeding their budget.C. Create an Amazon CloudWatch metric and a CloudWatch alarm for the application team's usage. Configure an AWS Lambda to use predefined tags to identify and stop nonessential services.This option involves setting up CloudWatch metrics and alarms, and using AWS Lambda for automated responses.While it can be configured to take certain actions (like stopping services), it does not provide a direct enforcement mechanism for the budget.It relies on predefined tags and potentially complex logic to identify and stop services, which may not be foolproof.D. Use AWS Cost Anomaly Detection to monitor the application team's usage and to alert the application team about unexpected spending patterns.AWS Cost Anomaly Detection helps identify unexpected spending patterns. It provides insights and alerts, but does not enforce budget limits. It relies on manual intervention to take corrective actions. Given these considerations, Option B provides the most suitable solution to meet the requirement:It sets a fixed monthly budget using AWS Budgets.It enforces the budget limit automatically by applying an SCP to the OU when the budget is reached. This ensures that the application team cannot exceed their budget without automated intervention.