Amazon AWS Certified Solutions Architect - Associate SAA-C03 Practice Test 32
Question 310
A set of independent task jobs must process queue entries and each may retry safely. Which consumer contract is critical?
- Grant the ECS task role necessary SQS permissions and allow cross-account access with the queue policy.
- Run an independent ECS worker service and scale it using queue backlog metrics.
- Acknowledge queue messages after durable completion and ensure idempotent task execution.
- Use an ECS rolling service deployment with appropriate minimum and maximum healthy percentages.
Explanation
Correct Answer
C:Task replacement and message visibility can cause retries; durable completion must precede deletion. Terminate a task mid-job and verify the next task completes exactly one logical side effect.
Incorrect Answers
A:Cross-account SQS access requires compatible identity and resource-based permissions. Acknowledge queue messages after durable completion and ensure idempotent task execution. Terminate a task mid-job and verify the next task completes exactly one logical side effect.
B:Independent worker tasks consume durable queue jobs and scale separately from request-serving tasks. Acknowledge queue messages after durable completion and ensure idempotent task execution. Terminate a task mid-job and verify the next task completes exactly one logical side effect.
D:The scheduler overlaps old and new healthy tasks during controlled replacement. Acknowledge queue messages after durable completion and ensure idempotent task execution. Terminate a task mid-job and verify the next task completes exactly one logical side effect.
Question 311
A microservice requires zero management of EC2 worker hosts and variable task-count scaling. Which compute launch type suits it?
- Deploy the worker as an independent ECS service behind an SQS queue.
- Configure ECS Service Connect or supported service discovery between services.
- Run an independent ECS worker service and scale it using queue backlog metrics.
- Run the ECS tasks on AWS Fargate with task-level CPU and memory choices.
Explanation
Correct Answer
D:Fargate removes EC2 host capacity management while retaining managed container task scheduling. Scale the service and verify no EC2 container-instance fleet must be managed.
Incorrect Answers
A:SQS buffers pending jobs while ECS replaces unhealthy worker tasks independent of API availability. Run the ECS tasks on AWS Fargate with task-level CPU and memory choices. Scale the service and verify no EC2 container-instance fleet must be managed.
B:Service-level endpoint names avoid hardcoding rapidly changing container IP addresses. Run the ECS tasks on AWS Fargate with task-level CPU and memory choices. Scale the service and verify no EC2 container-instance fleet must be managed.
C:Independent worker tasks consume durable queue jobs and scale separately from request-serving tasks. Run the ECS tasks on AWS Fargate with task-level CPU and memory choices. Scale the service and verify no EC2 container-instance fleet must be managed.
Question 312
A worker cluster needs to consume messages from a queue in a different AWS account. What authorization boundary must be configured?
- Deploy the worker as an independent ECS service behind an SQS queue.
- Grant the ECS task role necessary SQS permissions and allow cross-account access with the queue policy.
- Run an independent ECS worker service and scale it using queue backlog metrics.
- Run the ECS tasks on AWS Fargate with task-level CPU and memory choices.
Explanation
Correct Answer
B:Cross-account SQS access requires compatible identity and resource-based permissions. Invoke ReceiveMessage as the task role from the worker account and inspect authorization.
Incorrect Answers
A:SQS buffers pending jobs while ECS replaces unhealthy worker tasks independent of API availability. Grant the ECS task role necessary SQS permissions and allow cross-account access with the queue policy. Invoke ReceiveMessage as the task role from the worker account and inspect authorization.
C:Independent worker tasks consume durable queue jobs and scale separately from request-serving tasks. Grant the ECS task role necessary SQS permissions and allow cross-account access with the queue policy. Invoke ReceiveMessage as the task role from the worker account and inspect authorization.
D:Fargate removes EC2 host capacity management while retaining managed container task scheduling. Grant the ECS task role necessary SQS permissions and allow cross-account access with the queue policy. Invoke ReceiveMessage as the task role from the worker account and inspect authorization.
Question 313
A single EC2 instance handles all requests and fails during a traffic spike. Which scalable web topology should replace it?
- Place stateless application instances in an Auto Scaling group behind an Application Load Balancer.
- Place Auto Scaling instances across multiple suitable Availability Zones behind an ALB.
- Use an application-specific target-group health check and Auto Scaling health-check grace period.
- Route requests through an ALB DNS endpoint with registered Auto Scaling targets.
Explanation
Correct Answer
A:The ALB distributes requests while the group maintains and scales healthy instances. Load test and terminate one target while tracking successful requests and new capacity.
Incorrect Answers
B:Multi-AZ capacity spreads demand and reduces dependence on one AZ for new launches. Place stateless application instances in an Auto Scaling group behind an Application Load Balancer. Load test and terminate one target while tracking successful requests and new capacity.
C:Readiness checks and grace periods let instances initialize before serving or being judged unhealthy. Place stateless application instances in an Auto Scaling group behind an Application Load Balancer. Load test and terminate one target while tracking successful requests and new capacity.
D:A load balancer abstracts instance replacement; direct instance IPs defeat fleet elasticity. Place stateless application instances in an Auto Scaling group behind an Application Load Balancer. Load test and terminate one target while tracking successful requests and new capacity.
Question 314
An Auto Scaling group launches instances but incoming clients still point to one hardcoded instance IP. What must change?
- Put current startup instructions in a versioned launch template and approved configuration pipeline.
- Configure EC2 Auto Scaling target tracking for a representative utilization metric.
- Route requests through an ALB DNS endpoint with registered Auto Scaling targets.
- Place stateless application instances in an Auto Scaling group behind an Application Load Balancer.
Explanation
Correct Answer
C:A load balancer abstracts instance replacement; direct instance IPs defeat fleet elasticity. Replace a target and confirm the public endpoint remains stable.
Incorrect Answers
A:Consistent instance configuration is essential for safe replacement and horizontal scaling. Route requests through an ALB DNS endpoint with registered Auto Scaling targets. Replace a target and confirm the public endpoint remains stable.
B:Target tracking adjusts desired capacity to maintain a target metric across load changes. Route requests through an ALB DNS endpoint with registered Auto Scaling targets. Replace a target and confirm the public endpoint remains stable.
D:The ALB distributes requests while the group maintains and scales healthy instances. Route requests through an ALB DNS endpoint with registered Auto Scaling targets. Replace a target and confirm the public endpoint remains stable.
Question 315
A web fleet scales out, but user session state exists only in local instance memory. What architecture avoids session loss on new targets?
- Use an application-specific target-group health check and Auto Scaling health-check grace period.
- Place stateless application instances in an Auto Scaling group behind an Application Load Balancer.
- Configure EC2 Auto Scaling target tracking for a representative utilization metric.
- Externalize session state to a shared store such as ElastiCache or DynamoDB.
Explanation
Correct Answer
D:Shared sessions make application nodes interchangeable across replacements and scaling actions. Authenticate through one target and then force a different target to serve the session.
Incorrect Answers
A:Readiness checks and grace periods let instances initialize before serving or being judged unhealthy. Externalize session state to a shared store such as ElastiCache or DynamoDB. Authenticate through one target and then force a different target to serve the session.
B:The ALB distributes requests while the group maintains and scales healthy instances. Externalize session state to a shared store such as ElastiCache or DynamoDB. Authenticate through one target and then force a different target to serve the session.
C:Target tracking adjusts desired capacity to maintain a target metric across load changes. Externalize session state to a shared store such as ElastiCache or DynamoDB. Authenticate through one target and then force a different target to serve the session.
Question 316
Traffic increases during known daily peak hours and target tracking reacts too late. What complementary capacity policy helps?
- Configure EC2 Auto Scaling target tracking for a representative utilization metric.
- Place stateless application instances in an Auto Scaling group behind an Application Load Balancer.
- Place Auto Scaling instances across multiple suitable Availability Zones behind an ALB.
- Use scheduled Auto Scaling capacity adjustments before predictable peaks.
Explanation
Correct Answer
D:Scheduled scaling prepositions capacity for known demand while dynamic policies handle unexpected fluctuations. Confirm healthy capacity exists before the first peak requests arrive.
Incorrect Answers
A:Target tracking adjusts desired capacity to maintain a target metric across load changes. Use scheduled Auto Scaling capacity adjustments before predictable peaks. Confirm healthy capacity exists before the first peak requests arrive.
B:The ALB distributes requests while the group maintains and scales healthy instances. Use scheduled Auto Scaling capacity adjustments before predictable peaks. Confirm healthy capacity exists before the first peak requests arrive.
C:Multi-AZ capacity spreads demand and reduces dependence on one AZ for new launches. Use scheduled Auto Scaling capacity adjustments before predictable peaks. Confirm healthy capacity exists before the first peak requests arrive.
Question 317
An ALB sends traffic to newly launched EC2 instances before application initialization completes. What should be tuned?
- Use an application-specific target-group health check and Auto Scaling health-check grace period.
- Configure EC2 Auto Scaling target tracking for a representative utilization metric.
- Place stateless application instances in an Auto Scaling group behind an Application Load Balancer.
- Use scheduled Auto Scaling capacity adjustments before predictable peaks.
Explanation
Correct Answer
A:Readiness checks and grace periods let instances initialize before serving or being judged unhealthy. Delay application startup and verify the target is not selected until ready.
Incorrect Answers
B:Target tracking adjusts desired capacity to maintain a target metric across load changes. Use an application-specific target-group health check and Auto Scaling health-check grace period. Delay application startup and verify the target is not selected until ready.
C:The ALB distributes requests while the group maintains and scales healthy instances. Use an application-specific target-group health check and Auto Scaling health-check grace period. Delay application startup and verify the target is not selected until ready.
D:Scheduled scaling prepositions capacity for known demand while dynamic policies handle unexpected fluctuations. Use an application-specific target-group health check and Auto Scaling health-check grace period. Delay application startup and verify the target is not selected until ready.
Question 318
A service's throughput depends on average target CPU and load follows a variable daily curve. Which scaling policy is suitable?
- Configure EC2 Auto Scaling target tracking for a representative utilization metric.
- Use scheduled Auto Scaling capacity adjustments before predictable peaks.
- Place Auto Scaling instances across multiple suitable Availability Zones behind an ALB.
- Route requests through an ALB DNS endpoint with registered Auto Scaling targets.
Explanation
Correct Answer
A:Target tracking adjusts desired capacity to maintain a target metric across load changes. Generate varying traffic and compare metric, desired capacity, and response time.
Incorrect Answers
B:Scheduled scaling prepositions capacity for known demand while dynamic policies handle unexpected fluctuations. Configure EC2 Auto Scaling target tracking for a representative utilization metric. Generate varying traffic and compare metric, desired capacity, and response time.
C:Multi-AZ capacity spreads demand and reduces dependence on one AZ for new launches. Configure EC2 Auto Scaling target tracking for a representative utilization metric. Generate varying traffic and compare metric, desired capacity, and response time.
D:A load balancer abstracts instance replacement; direct instance IPs defeat fleet elasticity. Target tracking adjusts desired capacity to maintain a target metric across load changes.
Question 319
An instance repeatedly fails and is replaced, but the replacement uses outdated application configuration. What ensures reproducible launches?
- Put current startup instructions in a versioned launch template and approved configuration pipeline.
- Route requests through an ALB DNS endpoint with registered Auto Scaling targets.
- Configure EC2 Auto Scaling target tracking for a representative utilization metric.
- Externalize session state to a shared store such as ElastiCache or DynamoDB.
Explanation
Correct Answer
A:Consistent instance configuration is essential for safe replacement and horizontal scaling. Terminate a target and compare the new instance's application version and settings.
Incorrect Answers
B:A load balancer abstracts instance replacement; direct instance IPs defeat fleet elasticity. Put current startup instructions in a versioned launch template and approved configuration pipeline. Terminate a target and compare the new instance's application version and settings.
C:Target tracking adjusts desired capacity to maintain a target metric across load changes. Put current startup instructions in a versioned launch template and approved configuration pipeline. Terminate a target and compare the new instance's application version and settings.
D:Shared sessions make application nodes interchangeable across replacements and scaling actions. Put current startup instructions in a versioned launch template and approved configuration pipeline. Terminate a target and compare the new instance's application version and settings.
Question 320
A service experiences a regional burst beyond one AZ's capacity. How should capacity be distributed?
- Place stateless application instances in an Auto Scaling group behind an Application Load Balancer.
- Place Auto Scaling instances across multiple suitable Availability Zones behind an ALB.
- Use scheduled Auto Scaling capacity adjustments before predictable peaks.
- Route requests through an ALB DNS endpoint with registered Auto Scaling targets.
Explanation
Correct Answer
B:Multi-AZ capacity spreads demand and reduces dependence on one AZ for new launches. Disable an AZ and inspect remaining target capacity and request success.
Incorrect Answers
A:The ALB distributes requests while the group maintains and scales healthy instances. Place Auto Scaling instances across multiple suitable Availability Zones behind an ALB. Disable an AZ and inspect remaining target capacity and request success.
C:Scheduled scaling prepositions capacity for known demand while dynamic policies handle unexpected fluctuations. Place Auto Scaling instances across multiple suitable Availability Zones behind an ALB. Disable an AZ and inspect remaining target capacity and request success.
D:A load balancer abstracts instance replacement; direct instance IPs defeat fleet elasticity. Multi-AZ capacity spreads demand and reduces dependence on one AZ for new launches.