cert
cert-1
cert-2

Pass Amazon AWS Certified Solutions Architect - Associate SAA-C03 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers to Pass the Actual Exam!
30 Days Free Updates, Instant Download!

cert-5
cert-6
AWS Certified Solutions Architect - Associate SAA-C03 Exam - Verified By Experts
AWS Certified Solutions Architect - Associate SAA-C03 Premium Bundle
$29.98

AWS Certified Solutions Architect - Associate SAA-C03 Premium Bundle

$79.99
$109.97
  • Premium File 1063 Questions & Answers. Last update: Nov 10, 2026
  • Training Course 368 Video Lectures
  • Study Guide 632 Pages
 
$109.97
$79.99
accept 217 downloads in last 7 days
block-screenshots
Purchase Amazon AWS Certified Solutions Architect - Associate SAA-C03 Exam Training Products Individually
Amazon AWS Certified Solutions Architect - Associate SAA-C03 Premium File
Premium File 1063 Q&A
$76.99$69.99
Amazon AWS Certified Solutions Architect - Associate SAA-C03 Video Training Course
Training Course 368 Lectures
$21.99 $19.99
Amazon AWS Certified Solutions Architect - Associate SAA-C03 PDF Study Guide
Study Guide 632 Pages
$21.99 $19.99
Amazon AWS Certified Solutions Architect - Associate SAA-C03 Practice Test 36

Question 350

Users require session affinity for a legacy component during a short migration, while moving toward stateless nodes. Which load balancer setting can help temporarily?

  1. Use an ALB target-group deregistration delay with app-aware draining.
  2. Deploy targets across at least two Availability Zones behind an Application Load Balancer.
  3. Enable scoped ALB target-group stickiness with an appropriate duration.
  4. Create listener path-based routing rules with separate target groups.

Explanation

Correct Answer

C:

Target-group stickiness may keep a client on one target, though externalized state is preferable for full resilience. Make repeated requests with stickiness cookies and observe target selection.

Incorrect Answers

A:

Deregistration delay lets in-flight requests complete while new requests route elsewhere. Enable scoped ALB target-group stickiness with an appropriate duration. Make repeated requests with stickiness cookies and observe target selection.

B:

An ALB routes new requests to healthy targets in surviving enabled zones. Target-group stickiness may keep a client on one target, though externalized state is preferable for full resilience.

D:

ALB listener rules select target groups by HTTP path without deploying a second load balancer. Enable scoped ALB target-group stickiness with an appropriate duration. Make repeated requests with stickiness cookies and observe target selection.

Question 351

A load balancer is healthy but one application's health path incorrectly returns success even when its database is down. What should change?

  1. Make the readiness check reflect the application's critical dependency state.
  2. Deploy targets across at least two Availability Zones behind an Application Load Balancer.
  3. Enable the load balancer across multiple Availability Zone subnets with healthy targets.
  4. Use an ALB target-group deregistration delay with app-aware draining.

Explanation

Correct Answer

A:

A shallow process-only check can route users to instances that cannot serve useful requests. Simulate database unavailability and verify targets are removed from service when appropriate.

Incorrect Answers

B:

An ALB routes new requests to healthy targets in surviving enabled zones. Make the readiness check reflect the application's critical dependency state. Simulate database unavailability and verify targets are removed from service when appropriate.

C:

ALBs need enabled AZ subnet mappings to provide distributed load-balancing nodes and route to targets. Make the readiness check reflect the application's critical dependency state. Simulate database unavailability and verify targets are removed from service when appropriate.

D:

Deregistration delay lets in-flight requests complete while new requests route elsewhere. Make the readiness check reflect the application's critical dependency state. Simulate database unavailability and verify targets are removed from service when appropriate.

Question 352

An ALB's listeners are configured in only one subnet and fail to offer multi-AZ ingress capacity. What change is needed?

  1. Make the readiness check reflect the application's critical dependency state.
  2. Create listener path-based routing rules with separate target groups.
  3. Deploy targets across at least two Availability Zones behind an Application Load Balancer.
  4. Enable the load balancer across multiple Availability Zone subnets with healthy targets.

Explanation

Correct Answer

D:

ALBs need enabled AZ subnet mappings to provide distributed load-balancing nodes and route to targets. Inspect the enabled zones and simulate loss of one subnet or AZ.

Incorrect Answers

A:

A shallow process-only check can route users to instances that cannot serve useful requests. Enable the load balancer across multiple Availability Zone subnets with healthy targets. Inspect the enabled zones and simulate loss of one subnet or AZ.

B:

ALB listener rules select target groups by HTTP path without deploying a second load balancer. Enable the load balancer across multiple Availability Zone subnets with healthy targets. Inspect the enabled zones and simulate loss of one subnet or AZ.

C:

An ALB routes new requests to healthy targets in surviving enabled zones. Enable the load balancer across multiple Availability Zone subnets with healthy targets. Inspect the enabled zones and simulate loss of one subnet or AZ.

Question 353

An EC2 web fleet must remain available if an individual host or a whole Availability Zone fails. The fleet is fronted by an ALB, and failed targets should be replaced automatically. Which TWO Auto Scaling design controls support that requirement? (Select TWO.)

  1. Use a DNS TXT record as the only mechanism to relaunch failed EC2 instances.
  2. Pin all Auto Scaling instances to the same underlying host and one AZ for easier diagnostics.
  3. Use appropriate EC2 and ALB health checks so unhealthy instances are replaced to preserve desired capacity.
  4. Reduce Auto Scaling desired capacity to zero after one instance fails regardless of incoming demand.
  5. Configure the Auto Scaling group to launch replacement instances across at least two healthy Availability Zones.

Explanation

Correct Answers

C:

Health checks and ASG desired-capacity reconciliation replace failed targets rather than merely generating an alert.

E:

Distributing eligible instances across AZs reduces dependence on a single failure domain.

Incorrect Answers

A:

DNS records cannot create instances or coordinate Auto Scaling health replacement.

B:

Correlated placement makes the fleet vulnerable to the exact AZ or host loss described.

D:

Eliminating desired capacity prevents replacement and does not satisfy availability.

Question 354

An application deployment uses a single AZ and the entire tier disappears when that AZ fails. Which configuration reduces the single point of failure?

  1. Configure the Auto Scaling group's subnet list across multiple Availability Zones.
  2. Run an Auto Scaling instance refresh with health checks and rollback safeguards.
  3. Use an Auto Scaling lifecycle hook for the termination transition.
  4. Use Auto Scaling health checks and desired-capacity replacement of unhealthy instances.

Explanation

Correct Answer

A:

A group can place replacements in healthy zones when capacity is available. Simulate one AZ outage and verify active instances remain in another.

Incorrect Answers

B:

Instance refresh replaces fleet members systematically using the new launch configuration. Configure the Auto Scaling group's subnet list across multiple Availability Zones. Simulate one AZ outage and verify active instances remain in another.

C:

Lifecycle hooks pause transitions so cleanup logic can complete before the instance goes away. Configure the Auto Scaling group's subnet list across multiple Availability Zones. Simulate one AZ outage and verify active instances remain in another.

D:

An Auto Scaling group replaces instances found unhealthy according to EC2 or enabled load-balancer checks. Configure the Auto Scaling group's subnet list across multiple Availability Zones. Simulate one AZ outage and verify active instances remain in another.

Question 355

A replacement instance enters service before its user-data bootstrap finishes. Which timing mechanism is relevant?

  1. Use Auto Scaling health checks and desired-capacity replacement of unhealthy instances.
  2. Run an Auto Scaling instance refresh with health checks and rollback safeguards.
  3. The group may not have Elastic Load Balancing health checks enabled and needs that health source.
  4. Set an Auto Scaling health-check grace period and readiness checks aligned to bootstrap time.

Explanation

Correct Answer

D:

Grace periods reduce premature health failures during launch; target health checks gate traffic. Launch a slow-starting instance and confirm it is admitted after readiness.

Incorrect Answers

A:

An Auto Scaling group replaces instances found unhealthy according to EC2 or enabled load-balancer checks. Set an Auto Scaling health-check grace period and readiness checks aligned to bootstrap time. Launch a slow-starting instance and confirm it is admitted after readiness.

B:

Instance refresh replaces fleet members systematically using the new launch configuration. Set an Auto Scaling health-check grace period and readiness checks aligned to bootstrap time. Launch a slow-starting instance and confirm it is admitted after readiness.

C:

An EC2-only health check cannot automatically classify an application-unhealthy ALB target as unhealthy. Set an Auto Scaling health-check grace period and readiness checks aligned to bootstrap time. Launch a slow-starting instance and confirm it is admitted after readiness.

Question 356

A team drains EC2 connections during deployment and requires an extra cleanup action before termination. What should run?

  1. Move essential state to durable shared storage or a managed data store before relying on disposable nodes.
  2. Configure the Auto Scaling group's subnet list across multiple Availability Zones.
  3. Run an Auto Scaling instance refresh with health checks and rollback safeguards.
  4. Use an Auto Scaling lifecycle hook for the termination transition.

Explanation

Correct Answer

D:

Lifecycle hooks pause transitions so cleanup logic can complete before the instance goes away. Scale in a test target and inspect hook event completion and connection drain.

Incorrect Answers

A:

Auto Scaling may terminate and replace instances, so nonreplicated attached state is not inherently portable. Use an Auto Scaling lifecycle hook for the termination transition. Scale in a test target and inspect hook event completion and connection drain.

B:

A group can place replacements in healthy zones when capacity is available. Use an Auto Scaling lifecycle hook for the termination transition. Scale in a test target and inspect hook event completion and connection drain.

C:

Instance refresh replaces fleet members systematically using the new launch configuration. Use an Auto Scaling lifecycle hook for the termination transition. Scale in a test target and inspect hook event completion and connection drain.

Question 357

An application periodically needs twice the usual fleet size in one AZ, but the AZ capacity can be exhausted. How can the architect reduce impact?

  1. Distribute instance capacity across more AZs and use eligible instance-type flexibility.
  2. Configure the Auto Scaling group's subnet list across multiple Availability Zones.
  3. Run an Auto Scaling instance refresh with health checks and rollback safeguards.
  4. Use Auto Scaling health checks and desired-capacity replacement of unhealthy instances.

Explanation

Correct Answer

A:

Multi-AZ placement and compatible instance capacity options reduce dependency on one capacity pool. Force one instance type unavailable and verify healthy capacity can still launch elsewhere.

Incorrect Answers

B:

A group can place replacements in healthy zones when capacity is available. Distribute instance capacity across more AZs and use eligible instance-type flexibility. Force one instance type unavailable and verify healthy capacity can still launch elsewhere.

C:

Instance refresh replaces fleet members systematically using the new launch configuration. Distribute instance capacity across more AZs and use eligible instance-type flexibility. Force one instance type unavailable and verify healthy capacity can still launch elsewhere.

D:

An Auto Scaling group replaces instances found unhealthy according to EC2 or enabled load-balancer checks. Distribute instance capacity across more AZs and use eligible instance-type flexibility. Force one instance type unavailable and verify healthy capacity can still launch elsewhere.

Question 358

A new AMI deployment must roll safely with rollback if the new instances fail readiness. Which operation is suitable?

  1. Use an Auto Scaling lifecycle hook for the termination transition.
  2. Run an Auto Scaling instance refresh with health checks and rollback safeguards.
  3. Use Auto Scaling health checks and desired-capacity replacement of unhealthy instances.
  4. Set an Auto Scaling health-check grace period and readiness checks aligned to bootstrap time.

Explanation

Correct Answer

B:

Instance refresh replaces fleet members systematically using the new launch configuration. Deploy a failing AMI in staging and verify rollback or halted refresh behavior.

Incorrect Answers

A:

Lifecycle hooks pause transitions so cleanup logic can complete before the instance goes away. Run an Auto Scaling instance refresh with health checks and rollback safeguards. Deploy a failing AMI in staging and verify rollback or halted refresh behavior.

C:

An Auto Scaling group replaces instances found unhealthy according to EC2 or enabled load-balancer checks. Run an Auto Scaling instance refresh with health checks and rollback safeguards. Deploy a failing AMI in staging and verify rollback or halted refresh behavior.

D:

Grace periods reduce premature health failures during launch; target health checks gate traffic. Run an Auto Scaling instance refresh with health checks and rollback safeguards. Deploy a failing AMI in staging and verify rollback or halted refresh behavior.

Question 359

An instance is unhealthy at the ALB but its EC2 status checks remain healthy. Why might an Auto Scaling group fail to replace it?

  1. Set an Auto Scaling health-check grace period and readiness checks aligned to bootstrap time.
  2. Use Auto Scaling health checks and desired-capacity replacement of unhealthy instances.
  3. The group may not have Elastic Load Balancing health checks enabled and needs that health source.
  4. Configure the Auto Scaling group's subnet list across multiple Availability Zones.

Explanation

Correct Answer

C:

An EC2-only health check cannot automatically classify an application-unhealthy ALB target as unhealthy. Enable the correct group health-check type and verify replacement after an application failure.

Incorrect Answers

A:

Grace periods reduce premature health failures during launch; target health checks gate traffic. The group may not have Elastic Load Balancing health checks enabled and needs that health source. Enable the correct group health-check type and verify replacement after an application failure.

B:

An Auto Scaling group replaces instances found unhealthy according to EC2 or enabled load-balancer checks. The group may not have Elastic Load Balancing health checks enabled and needs that health source. Enable the correct group health-check type and verify replacement after an application failure.

D:

A group can place replacements in healthy zones when capacity is available. An EC2-only health check cannot automatically classify an application-unhealthy ALB target as unhealthy.

Question 360

A worker instance has an attached EBS volume with irreplaceable local state. Why is simple Auto Scaling replacement unsafe?

  1. Move essential state to durable shared storage or a managed data store before relying on disposable nodes.
  2. Use Auto Scaling health checks and desired-capacity replacement of unhealthy instances.
  3. Use an Auto Scaling lifecycle hook for the termination transition.
  4. Configure the Auto Scaling group's subnet list across multiple Availability Zones.

Explanation

Correct Answer

A:

Auto Scaling may terminate and replace instances, so nonreplicated attached state is not inherently portable. Terminate a test instance and confirm the needed data remains accessible.

Incorrect Answers

B:

An Auto Scaling group replaces instances found unhealthy according to EC2 or enabled load-balancer checks. Move essential state to durable shared storage or a managed data store before relying on disposable nodes. Terminate a test instance and confirm the needed data remains accessible.

C:

Lifecycle hooks pause transitions so cleanup logic can complete before the instance goes away. Move essential state to durable shared storage or a managed data store before relying on disposable nodes. Terminate a test instance and confirm the needed data remains accessible.

D:

A group can place replacements in healthy zones when capacity is available. Move essential state to durable shared storage or a managed data store before relying on disposable nodes. Terminate a test instance and confirm the needed data remains accessible.

AWS Certified Solutions Architect - Associate SAA-C03 Practice Tests