AWS Certified Solutions Architect Professional SAP-C02 Practice Question
A startup is refactoring its stateless microservice API that currently runs on EC2 instances. Baseline traffic is about 100 requests per minute, but social-media campaigns can cause spikes of up to 10 000 requests per minute that last 15-30 minutes. The 95th-percentile backend response time must stay below 200 ms during spikes, compute cost must be as low as possible when demand is minimal, and the five-person operations team must not manage server patching or cluster capacity. Which architecture best satisfies these business objectives?
Run the containers in an Amazon ECS service using AWS Fargate. Define a capacity-provider strategy that assigns a higher weight to FARGATE_SPOT than FARGATE, set the desired task count between 1 and 300, and attach a target-tracking scaling policy on the ALBRequestCountPerTarget metric to keep the average load at 50 requests per task.
Repackage the workload as AWS Lambda functions behind Amazon API Gateway and configure 1 000 units of Provisioned Concurrency for each function.
Deploy the containers to an Amazon ECS cluster backed by an EC2 Auto Scaling group of c6i.large On-Demand instances and use a target-tracking scaling policy that keeps average CPU utilization at 60 percent with predictive scaling enabled.
Run the containers on an Amazon EKS cluster that uses only Spot Instances managed by Cluster Autoscaler and Karpenter, keeping one node permanently in the cluster.
Running the containers in an Amazon ECS service on AWS Fargate removes the need to manage servers or clusters. A target-tracking scaling policy on the ALBRequestCountPerTarget metric automatically adds or removes tasks so that each task handles roughly the specified number of requests, allowing the service to scale from one task during idle periods to hundreds of tasks within minutes and keep latency under 200 ms. A capacity-provider strategy that gives higher weight to FARGATE_SPOT than FARGATE launches tasks on discounted Fargate Spot whenever spare capacity is available, cutting compute cost by up to 70 percent, while still permitting on-demand Fargate tasks if Spot capacity is unavailable. The alternative solutions either retain idle EC2 or Provisioned Concurrency capacity, add operational overhead, or rely solely on Spot Instances without a cost-effective fallback, so they do not meet both the cost and performance goals as effectively.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is AWS Fargate and how does it eliminate the need to manage servers?
Open an interactive chat with Bash
What is a capacity-provider strategy and how do FARGATE_SPOT and FARGATE work together?
Open an interactive chat with Bash
How does the ALBRequestCountPerTarget metric support auto-scaling in this solution?
Open an interactive chat with Bash
AWS Certified Solutions Architect Professional SAP-C02
Design for New Solutions
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
IT & Cybersecurity Package Join Premium for Full Access