Cost Management & Support

AWS Budgets allows users to set custom financial limits and receive alerts when costs exceed or are forecasted to exceed the budgeted amount. This makes it the appropriate choice for setting up alerts for monthly spending.

AWS Cost Allocation Tags allow businesses to categorize and track AWS costs by assigning tags to resources, enabling cost management by department.

AWS Budgets allows users to set up alerts for when forecasted costs are expected to exceed a set budget, making it the appropriate service for this scenario.

Enterprise On-Ramp provides a 30-minute response time for critical system failures, which is suitable for business-critical applications.

Option B is correct because consolidated billing provides a single bill for multiple AWS accounts and combines eligible usage across accounts for applicable volume pricing, Reserved Instance discounts, and Savings Plans benefits. Option C is correct because AWS Organizations provides the multi-account structure through which consolidated billing is managed, with a management account responsible for payment of member-account charges. Option A is incorrect because Cost Allocation Tags are used to categorize and track costs by tagged resources, not to consolidate account billing or combine usage for volume pricing. Option D is incorrect because AWS Pricing Calculator estimates the cost of planned AWS workloads rather than managing active multi-account billing. Option E is incorrect because AWS Cost Explorer analyzes and visualizes cost and usage data but does not provide the organization's consolidated billing mechanism. Reference: AWS Organizations and Consolidated Billing documentation.

Option B is correct because AWS Compute Optimizer analyzes the configuration and utilization metrics of supported AWS resources and generates recommendations for optimizing resources such as Amazon EC2 instances and EC2 Auto Scaling groups. Option D is correct because AWS Trusted Advisor evaluates AWS environments against best-practice checks, including cost optimization checks such as unassociated Elastic IP addresses and underutilized resources. Option A is incorrect because AWS Systems Manager is primarily used for operational management, automation, and tasks such as patch management rather than workload rightsizing recommendations. Option C is incorrect because AWS Migration Evaluator is designed primarily to build data-driven business cases and analyze on-premises environments for migration planning. Option E is incorrect because AWS CloudTrail records and audits AWS API activity rather than providing resource rightsizing or cost optimization recommendations. Reference: AWS Compute Optimizer and AWS Trusted Advisor documentation.

Option C is correct because AWS Budgets allows organizations to define cost or usage budgets and configure alerts based on actual or forecasted spending relative to those thresholds. Option E is correct because AWS Trusted Advisor provides cost optimization checks that can identify specific idle or underutilized resources, including unassociated Elastic IP addresses, idle load balancers, and underutilized EBS volumes. Option A is incorrect because AWS CloudTrail records API activity for auditing and governance rather than providing cost threshold management or resource cost optimization checks. Option B is incorrect because AWS Cost Explorer is used to analyze and visualize cost and usage data but is not the primary service for predefined budget-threshold alerts. Option D is incorrect because AWS Compute Optimizer provides optimization recommendations for supported resources based on configuration and utilization metrics, rather than serving as the broad cost-optimization check service described in the question. Reference: AWS Trusted Advisor and AWS Budgets documentation.

Option B is correct because Enterprise Support provides a 15-minute response time for business-critical system-down cases, satisfying the requirement of 30 minutes or less. Option D is correct because Enterprise On-Ramp provides a 30-minute response time for business-critical system-down cases. Option A is incorrect because Business Support provides a one-hour response time for production system-down cases. Option C is incorrect because Developer Support provides technical support during business hours and does not provide the required 30-minute response time. Option E is incorrect because Basic Support does not provide technical support case response SLAs. Reference: AWS Support response-time documentation and AWS Compare Support Plans.