SAA-C03 Design Resilient Architectures Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  CloudFront caching with appropriate TTLs

  Why this is correct

  CloudFront caches objects at edge locations, so even when the S3 origin becomes temporarily unavailable, requests for cached content can be served from the edge as long as the TTL has not expired. If configured with error caching or a sufficiently long TTL, CloudFront can continue serving stale content during an origin failure, acting as a resilience buffer rather than merely a latency optimization. Selecting appropriate TTLs is therefore critical to making the static website tolerant to brief S3 outages.

• ✗

  AWS Backup Vault Lock

  Why it's wrong here

  AWS Backup Vault Lock is a feature of AWS Backup that enforces immutable (Write Once, Read Many) retention on backup vaults, preventing deletion or modification of recovery points for compliance purposes. It manages backup lifecycle policies and never interacts with S3 website content, CloudFront distributions, or edge caches. Enabling it does nothing to keep a static site available when the S3 origin is unreachable, because it exists solely to protect backups from tampering.

• ✗

  IAM Access Analyzer

  Why it's wrong here

  IAM Access Analyzer is a security auditing tool that analyzes S3 bucket policies and other resource policies to identify when resources are shared with external principals. It generates findings about potential unauthorized access but has no role in storing, caching, or delivering web content. This makes it entirely irrelevant to origin outage tolerance; it cannot serve cached objects or reroute traffic to alternate locations during an S3 disruption.

• ✗

  S3 Select

  Why it's wrong here

  S3 Select is a data retrieval feature that runs SQL queries directly against objects stored in S3, returning only a subset of rows or columns to reduce data transfer and compute overhead for analytical workloads. It operates on the existing object via the S3 API and does not replicate, cache, or create alternate copies of website assets. If the S3 bucket is temporarily unavailable, S3 Select requests fail just like any other S3 GET, so it provides zero benefit for keeping the static website accessible during an outage.

Go deeper

Related to this question