Home / SAA-C03 / Objective 4.2

Domain 4: Design Cost-Optimized Architectures · 20% of the exam · Full exam outline

4.2 Design cost-optimized compute solutions

What this objective covers · 5% of the exam

AWS cost management service features (for example, cost allocation tags, multi-account billing); AWS cost management tools with appropriate use cases (for example, AWS Cost Explorer, AWS Budgets, AWS Cost and Usage Report); AWS global infrastructure (for example, Availability Zones, AWS Regions); AWS purchasing options (for example, Spot Instances, Reserved Instances, Savings Plans); Distributed compute strategies (for example, edge processing); Hybrid compute options (for example, AWS Outposts); Instance types, families, and sizes (for example, memory optimized, compute optimized, virtualization); Optimization of compute utilization (for example, containers, serverless computing, microservices); Scaling strategies (for example, auto scaling, hibernation); Determining an appropriate load balancing strategy (for example, Application Load Balancer [Layer 7] compared with Network Load Balancer [Layer 4] compared with Gateway Load Balancer); Determining appropriate scaling methods and strategies for elastic workloads (for example, horizontal compared with vertical, EC2 hibernation); Determining cost-effective AWS compute services with appropriate use cases (for example, AWS Lambda, Amazon EC2, AWS Fargate); Determining the required availability for different classes of workloads (for example, production workloads, non-production workloads); Selecting the appropriate instance family for a workload; Selecting the appropriate instance size for a workload

Practice questions

Question 1easy

A cost review suggests that many EC2 instances in a production account are larger than they need to be. The team wants recommendations for better instance types and sizes based on each instance's actual CPU, memory, network and disk utilization, with projected utilization for each recommendation. Which service should it use?

Included in Sample: sample every domain.See plans

Choose an answer to check it. Afterward, select any option to review its explanation.

Budgets tracks spend and usage against thresholds and can alert or act, but it does not analyze instance utilization or recommend instance types.

CUR delivers detailed billing line items to S3 for analysis, which helps find expensive instances. It contains no rightsizing recommendations or projected utilization.

Compute Optimizer analyzes resource configuration and CloudWatch utilization metrics to produce rightsizing recommendations and flag idle resources. It shows projected utilization for each option so the team can weigh price against performance, after opting in.

Cost Explorer is the natural place to see that EC2 spend is high, and it recommends Reserved Instance purchases. It analyzes costs and usage rather than each instance's utilization metrics, so it does not say which smaller type or size fits.

Question 2easy

A car parts plant runs quality-inspection software on EC2 that must respond with very low latency to machinery on the factory floor, and its production data must be processed on site. The team wants to keep using the same AWS APIs, tools and services it uses in the Region. Which option fits?

Included in Master: master every domain.See plans