Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

Request the relevant quota increase and design tested capacity fallbacks solves the related scenario An Auto Scaling group cannot satisfy demand after reaching its service quota; capacity limits can prevent scaling policies from obtaining required instances.

Although Use a target-tracking metric representing request load or concurrency rather than CPU alone can be valid when An application scales only when CPU rises, but API latency is already high from request concurrency, it targets a different technical condition. Workload-aligned scaling responds to the actual bottleneck.

Enforce rate limits, queue buffering and bounded worker concurrency would address a different requirement: A service experiences a sudden 50-fold traffic burst and must avoid exhausting its downstream database. Admission controls protect downstream saturation during abrupt bursts.

This alternative, Implement Route 53 weighted routing with specified nonzero record weights, is appropriate when A team wants 15% of users to exercise a new regional stack using DNS rather than code changes. Weighted DNS response distribution enables a planned partial rollout.

For the separate situation A DNS name has several independent healthy web servers and must return multiple IPs while excluding failed hosts, Use Route 53 multivalue answer records with individual health checks could be useful. Multivalue answer routing returns up to eight healthy records rather than a single global anycast ingress.

Use CloudFront distributions with appropriate cache behaviors and multiple origins solves the related scenario Static media should be cached near users worldwide but dynamic APIs remain at regional origins; edge caching lowers latency for static content while routing dynamic requests to application origins.

This alternative, Configure Route 53 latency routing and endpoint health monitoring, is appropriate when Global users require a low-latency regional endpoint selected by measured network performance. Latency routing chooses AWS Regions based on observed DNS resolver path latency.

For the separate situation A DNS name has several independent healthy web servers and must return multiple IPs while excluding failed hosts, Use Route 53 multivalue answer records with individual health checks could be useful. Multivalue answer routing returns up to eight healthy records rather than a single global anycast ingress.

Use CloudFront distributions with appropriate cache behaviors and multiple origins solves the related scenario Static media should be cached near users worldwide but dynamic APIs remain at regional origins; edge caching lowers latency for static content while routing dynamic requests to application origins.

Configure Route 53 active-passive failover routing records solves the related scenario A disaster-recovery domain must prefer its main origin until health checks fail; failover policy selects a secondary response only when health conditions require it.

Although Implement Route 53 weighted routing with specified nonzero record weights can be valid when A team wants 15% of users to exercise a new regional stack using DNS rather than code changes, it targets a different technical condition. Weighted DNS response distribution enables a planned partial rollout.

Configure Route 53 latency routing and endpoint health monitoring would address a different requirement: Global users require a low-latency regional endpoint selected by measured network performance. Latency routing chooses AWS Regions based on observed DNS resolver path latency.

Implement Route 53 weighted routing with specified nonzero record weights solves the related scenario A team wants 15% of users to exercise a new regional stack using DNS rather than code changes; weighted DNS response distribution enables a planned partial rollout.

Although Configure Route 53 latency routing and endpoint health monitoring can be valid when Global users require a low-latency regional endpoint selected by measured network performance, it targets a different technical condition. Latency routing chooses AWS Regions based on observed DNS resolver path latency.

Use Route 53 multivalue answer records with individual health checks would address a different requirement: A DNS name has several independent healthy web servers and must return multiple IPs while excluding failed hosts. Multivalue answer routing returns up to eight healthy records rather than a single global anycast ingress.

Although Configure Route 53 active-passive failover routing records can be valid when A disaster-recovery domain must prefer its main origin until health checks fail, it targets a different technical condition. Failover policy selects a secondary response only when health conditions require it.

This alternative, Use Route 53 multivalue answer records with individual health checks, is appropriate when A DNS name has several independent healthy web servers and must return multiple IPs while excluding failed hosts. Multivalue answer routing returns up to eight healthy records rather than a single global anycast ingress.

For the separate situation Static media should be cached near users worldwide but dynamic APIs remain at regional origins, Use CloudFront distributions with appropriate cache behaviors and multiple origins could be useful. Edge caching lowers latency for static content while routing dynamic requests to application origins.

This alternative, Externalize state into durable shared storage or a database before enabling automated replacement, is appropriate when A worker writes task state solely to its ephemeral instance store and loses it when replaced. Stateless workers can be replaced safely only when critical state survives instance loss.

For the separate situation A core ingestion pipeline must buffer high-frequency writes during temporary database throttling, Introduce an SQS or Kinesis buffering tier with backpressure-aware consumers could be useful. Buffering separates producer availability from short periods of downstream saturation.

Although Configure bounded timeouts, jittered retries and circuit breakers can be valid when An application retries failing synchronous dependencies indefinitely and causes cascading timeouts, it targets a different technical condition. Controlled retry budgets prevent retry storms and resource exhaustion.

For the separate situation A core ingestion pipeline must buffer high-frequency writes during temporary database throttling, Introduce an SQS or Kinesis buffering tier with backpressure-aware consumers could be useful. Buffering separates producer availability from short periods of downstream saturation.

Configure bounded timeouts, jittered retries and circuit breakers solves the related scenario An application retries failing synchronous dependencies indefinitely and causes cascading timeouts; controlled retry budgets prevent retry storms and resource exhaustion.

Although Enable an appropriate database Multi-AZ deployment and test failover can be valid when A busy database suffers one-AZ outages that require manual restore from nightly snapshots, it targets a different technical condition. Multi-AZ synchronous standby provides operational recovery faster than backup-only restore.

Introduce an SQS or Kinesis buffering tier with backpressure-aware consumers solves the related scenario A core ingestion pipeline must buffer high-frequency writes during temporary database throttling; buffering separates producer availability from short periods of downstream saturation.

Although Spread Auto Scaling capacity and target health across the supported load-balancer AZs can be valid when An ALB serves three AZs but all Auto Scaling instances run in one AZ, it targets a different technical condition. Multi-AZ frontend alone does not protect a single-AZ application fleet.

Externalize state into durable shared storage or a database before enabling automated replacement would address a different requirement: A worker writes task state solely to its ephemeral instance store and loses it when replaced. Stateless workers can be replaced safely only when critical state survives instance loss.

Spread Auto Scaling capacity and target health across the supported load-balancer AZs would address a different requirement: An ALB serves three AZs but all Auto Scaling instances run in one AZ. Multi-AZ frontend alone does not protect a single-AZ application fleet.

This alternative, Externalize state into durable shared storage or a database before enabling automated replacement, is appropriate when A worker writes task state solely to its ephemeral instance store and loses it when replaced. Stateless workers can be replaced safely only when critical state survives instance loss.

For the separate situation An application retries failing synchronous dependencies indefinitely and causes cascading timeouts, Configure bounded timeouts, jittered retries and circuit breakers could be useful. Controlled retry budgets prevent retry storms and resource exhaustion.

Enable an appropriate database Multi-AZ deployment and test failover would address a different requirement: A busy database suffers one-AZ outages that require manual restore from nightly snapshots. Multi-AZ synchronous standby provides operational recovery faster than backup-only restore.

This alternative, Introduce an SQS or Kinesis buffering tier with backpressure-aware consumers, is appropriate when A core ingestion pipeline must buffer high-frequency writes during temporary database throttling. Buffering separates producer availability from short periods of downstream saturation.

For the separate situation An ALB serves three AZs but all Auto Scaling instances run in one AZ, Spread Auto Scaling capacity and target health across the supported load-balancer AZs could be useful. Multi-AZ frontend alone does not protect a single-AZ application fleet.