DOP-C02 Resilient Cloud Solutions 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.

• ✗

  Use Lambda@Edge to run functions at AWS edge locations

  Why it's wrong here

  Lambda@Edge executes your code at CloudFront edge locations, which are globally distributed points of presence, not AWS Regions. Edge locations lack core services such as DynamoDB or API Gateway, provide minimal durable storage, and a failed pop simply routes to the next edge or origin. Thus, it does not create independent regional data planes and leaves the application vulnerable to a single-Region outage.

• ✗

  Use DynamoDB auto-scaling and run Lambda in a single Region

  Why it's wrong here

  DynamoDB auto-scaling only adjusts read/write capacity within the same table and Region; it never creates replicas elsewhere, and running Lambda in one Region is a single point of failure. If that entire Region is lost, both the table and the function endpoint are unreachable, and no traffic can be shifted. This configuration optimizes capacity but does not provide disaster recovery.

• ✓

  Use DynamoDB global tables with Lambda functions deployed in multiple Regions and Route 53 multi-Region routing

  Why this is correct

  DynamoDB global tables asynchronously replicate writes to multiple Regions, providing active-active tables with automatic conflict resolution. Deploying Lambda in each Region makes stateless compute locally available, while Route 53 multi-Region routing (for example, failover or latency routing) sends traffic to a healthy Region. Together, these components form a resilient multi-Region serverless architecture with no single Region dependency.

• ✗

  Use DynamoDB Accelerator (DAX) to cache data across Regions

  Why it's wrong here

  DAX is an in-memory acceleration cluster for DynamoDB that lives in a single VPC and a single Region; it caches frequently accessed items to reduce latency, but offers zero data replication or failover capability. If the Region fails, the cache and the underlying table are both lost, so DAX cannot act as a disaster-recovery mechanism. It is strictly a performance optimization, not a resilience feature.

Go deeper

Related to this question