Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

Store sessions in a resilient shared service and spread stateless application hosts across AZs would address a different requirement: A private application must survive one AZ becoming unavailable without moving stateful sessions to a dead node. Externalizing session state permits healthy hosts to serve requests after AZ loss.

This alternative, Enable the cache engine's supported multi-AZ replica and automatic failover features, is appropriate when A cache cluster loses its primary node and needs fast automatic recovery. Replicas and failover promote healthy capacity when the primary fails.

Use an Auto Scaling group spanning AZs behind an Application Load Balancer solves the related scenario A web application needs to replace failed EC2 hosts while serving traffic through two or more AZs; aSG health replacement and ALB target routing reduce single-instance failures.

For the separate situation Restoration auditors need evidence that an encrypted backup can actually boot and serve its application, Schedule AWS Backup restore testing with application validation procedures could be useful. Restore tests validate recovery feasibility beyond successful backup-job status.

Use S3 versioning with suitable lifecycle and Object Lock retention requirements solves the related scenario Legal retention requires seven years of point-in-time file history on S3; versioning and retention protect historic object versions independently of overwrite events.

Use supported cross-account backup-copy policies and a separate backup account would address a different requirement: Critical workloads require a backup copy outside the source account's administrative blast radius. Account-separated copies reduce loss when the production account is compromised.

Schedule AWS Backup restore testing with application validation procedures solves the related scenario Restoration auditors need evidence that an encrypted backup can actually boot and serve its application; restore tests validate recovery feasibility beyond successful backup-job status.

Apply organization-aware AWS Backup policies with delegated administration and vaults would address a different requirement: Many accounts need common backup policies for EC2 and supported managed databases. Central governance coordinates backup schedules across supported protected resources.

This alternative, Use supported cross-account backup-copy policies and a separate backup account, is appropriate when Critical workloads require a backup copy outside the source account's administrative blast radius. Account-separated copies reduce loss when the production account is compromised.

Although Apply organization-aware AWS Backup policies with delegated administration and vaults can be valid when Many accounts need common backup policies for EC2 and supported managed databases, it targets a different technical condition. Central governance coordinates backup schedules across supported protected resources.

Use AWS Backup Vault Lock in compliance mode with properly configured retention would address a different requirement: Ransomware responders need backup copies that administrators cannot prematurely delete. Compliance-mode Vault Lock protects qualifying recovery points against unauthorized deletion.

This alternative, Use S3 versioning with suitable lifecycle and Object Lock retention requirements, is appropriate when Legal retention requires seven years of point-in-time file history on S3. Versioning and retention protect historic object versions independently of overwrite events.

This alternative, Use supported cross-account backup-copy policies and a separate backup account, is appropriate when Critical workloads require a backup copy outside the source account's administrative blast radius. Account-separated copies reduce loss when the production account is compromised.

For the separate situation Legal retention requires seven years of point-in-time file history on S3, Use S3 versioning with suitable lifecycle and Object Lock retention requirements could be useful. Versioning and retention protect historic object versions independently of overwrite events.

Apply organization-aware AWS Backup policies with delegated administration and vaults solves the related scenario Many accounts need common backup policies for EC2 and supported managed databases; central governance coordinates backup schedules across supported protected resources.

For the separate situation Restoration auditors need evidence that an encrypted backup can actually boot and serve its application, Schedule AWS Backup restore testing with application validation procedures could be useful. Restore tests validate recovery feasibility beyond successful backup-job status.

Use AWS Backup Vault Lock in compliance mode with properly configured retention solves the related scenario Ransomware responders need backup copies that administrators cannot prematurely delete; compliance-mode Vault Lock protects qualifying recovery points against unauthorized deletion.

Although Use supported cross-account backup-copy policies and a separate backup account can be valid when Critical workloads require a backup copy outside the source account's administrative blast radius, it targets a different technical condition. Account-separated copies reduce loss when the production account is compromised.

Use AWS Global Accelerator with regional endpoint groups and health checks solves the related scenario A website requires fixed anycast ingress IPs plus health-based movement between regional ALBs; global Accelerator exposes static anycast addresses and shifts new flows to healthy endpoints.

Configure Route 53 latency-based routing with regional health checks would address a different requirement: Clients on several continents should reach the lowest-latency healthy regional web endpoint. Latency routing chooses a suitable measured Region rather than a fixed geography.

This alternative, Choose Route 53 geolocation routing with an explicit default record, is appropriate when A multinational marketing site must select regional content origins using the country associated with its DNS queries. Geolocation routing selects DNS answers by estimated query origin and is not a substitute for strict end-user geofencing.

Configure Route 53 weighted routing records for the planned traffic split would address a different requirement: A controlled new regional launch should receive approximately 5% of DNS responses before broader adoption. Weighted DNS records distribute answer selection by relative record weights, though client caching affects actual request fractions.

This alternative, Choose Route 53 geolocation routing with an explicit default record, is appropriate when A multinational marketing site must select regional content origins using the country associated with its DNS queries. Geolocation routing selects DNS answers by estimated query origin and is not a substitute for strict end-user geofencing.

For the separate situation A website requires fixed anycast ingress IPs plus health-based movement between regional ALBs, Use AWS Global Accelerator with regional endpoint groups and health checks could be useful. Global Accelerator exposes static anycast addresses and shifts new flows to healthy endpoints.

Configure Route 53 latency-based routing with regional health checks would address a different requirement: Clients on several continents should reach the lowest-latency healthy regional web endpoint. Latency routing chooses a suitable measured Region rather than a fixed geography.

For the separate situation A multinational marketing site must select regional content origins using the country associated with its DNS queries, Choose Route 53 geolocation routing with an explicit default record could be useful. Geolocation routing selects DNS answers by estimated query origin and is not a substitute for strict end-user geofencing.

Use Route 53 failover records with meaningful health checks and tested DNS behavior solves the related scenario A primary region's HTTPS endpoint fails and users must move to a healthy standby origin; failover routing selects the secondary when the primary is considered unhealthy.

For the separate situation A website requires fixed anycast ingress IPs plus health-based movement between regional ALBs, Use AWS Global Accelerator with regional endpoint groups and health checks could be useful. Global Accelerator exposes static anycast addresses and shifts new flows to healthy endpoints.

Use Route 53 failover records with meaningful health checks and tested DNS behavior solves the related scenario A primary region's HTTPS endpoint fails and users must move to a healthy standby origin; failover routing selects the secondary when the primary is considered unhealthy.

Although Configure Route 53 latency-based routing with regional health checks can be valid when Clients on several continents should reach the lowest-latency healthy regional web endpoint, it targets a different technical condition. Latency routing chooses a suitable measured Region rather than a fixed geography.

Use Route 53 failover records with meaningful health checks and tested DNS behavior solves the related scenario A primary region's HTTPS endpoint fails and users must move to a healthy standby origin; failover routing selects the secondary when the primary is considered unhealthy.

Although Configure Route 53 weighted routing records for the planned traffic split can be valid when A controlled new regional launch should receive approximately 5% of DNS responses before broader adoption, it targets a different technical condition. Weighted DNS records distribute answer selection by relative record weights, though client caching affects actual request fractions.

Choose Route 53 geolocation routing with an explicit default record would address a different requirement: A multinational marketing site must select regional content origins using the country associated with its DNS queries. Geolocation routing selects DNS answers by estimated query origin and is not a substitute for strict end-user geofencing.