Amazon AWS Certified Solutions Architect - Associate SAA-C03 Practice Test 56
Question 550
A relational service runs steady high-volume transactions and already knows its capacity envelope. What Aurora deployment may fit?
- Add reader instances and direct query traffic through the reader endpoint.
- Use Aurora Serverless v2 with appropriate minimum and maximum ACU configuration.
- Provision eligible replicas in other AZs for fast DB instance failover.
- Use appropriately provisioned Aurora instances with replicas and capacity planning.
Explanation
Correct Answer
D:Provisioned Aurora suits sustained predictable throughput and explicit instance sizing. Benchmark steady-state transactions per second.
Incorrect Answers
A:Aurora Replicas share cluster storage while providing read compute scale. Use appropriately provisioned Aurora instances with replicas and capacity planning. Benchmark steady-state transactions per second.
B:Aurora Serverless v2 scales supported database compute in response to changing demand. Use appropriately provisioned Aurora instances with replicas and capacity planning. Benchmark steady-state transactions per second.
C:Resilient storage does not by itself provide an alternate running DB compute instance. Use appropriately provisioned Aurora instances with replicas and capacity planning. Benchmark steady-state transactions per second.
Question 551
A service needs PostgreSQL-compatible SQL features but the team proposes DynamoDB for auto scaling. What engine type should be assessed?
- Choose an appropriate relational engine such as Aurora PostgreSQL-compatible when SQL semantics are mandatory.
- Account for regional write ownership and replication lag in the app design.
- Add reader instances and direct query traffic through the reader endpoint.
- Use Aurora Serverless v2 with appropriate minimum and maximum ACU configuration.
Explanation
Correct Answer
A:Database type must match transaction, join and query behavior, not elasticity alone. Run the existing SQL integration tests.
Incorrect Answers
B:Aurora Global Database does not behave like an automatically conflict-free global multiwriter SQL database. Choose an appropriate relational engine such as Aurora PostgreSQL-compatible when SQL semantics are mandatory. Run the existing SQL integration tests.
C:Aurora Replicas share cluster storage while providing read compute scale. Choose an appropriate relational engine such as Aurora PostgreSQL-compatible when SQL semantics are mandatory. Run the existing SQL integration tests.
D:Aurora Serverless v2 scales supported database compute in response to changing demand. Choose an appropriate relational engine such as Aurora PostgreSQL-compatible when SQL semantics are mandatory. Run the existing SQL integration tests.
Question 552
An application needs globally distributed key-value lookups with predictable millisecond latency and flexible schema. Which data store is suitable?
- Use appropriately provisioned Aurora instances with replicas and capacity planning.
- Evaluate DynamoDB instead of relational instances for supported key-value patterns.
- Choose an appropriate relational engine such as Aurora PostgreSQL-compatible when SQL semantics are mandatory.
- Use Aurora Serverless v2 with appropriate minimum and maximum ACU configuration.
Explanation
Correct Answer
B:DynamoDB is purpose-built for scalable key-value and document data access. Test key-based response latency at target load.
Incorrect Answers
A:Provisioned Aurora suits sustained predictable throughput and explicit instance sizing. Evaluate DynamoDB instead of relational instances for supported key-value patterns. Test key-based response latency at target load.
C:Database type must match transaction, join and query behavior, not elasticity alone. Evaluate DynamoDB instead of relational instances for supported key-value patterns. Test key-based response latency at target load.
D:Aurora Serverless v2 scales supported database compute in response to changing demand. Evaluate DynamoDB instead of relational instances for supported key-value patterns. Test key-based response latency at target load.
Question 553
A global Aurora database has a writable primary Region and asynchronous read clusters elsewhere. What tradeoff matters?
- Add reader instances and direct query traffic through the reader endpoint.
- Account for regional write ownership and replication lag in the app design.
- Use Aurora Serverless v2 with appropriate minimum and maximum ACU configuration.
- Use appropriately provisioned Aurora instances with replicas and capacity planning.
Explanation
Correct Answer
B:Aurora Global Database does not behave like an automatically conflict-free global multiwriter SQL database. Try write and read routing during a controlled failover.
Incorrect Answers
A:Aurora Replicas share cluster storage while providing read compute scale. Account for regional write ownership and replication lag in the app design. Try write and read routing during a controlled failover.
C:Aurora Serverless v2 scales supported database compute in response to changing demand. Account for regional write ownership and replication lag in the app design. Try write and read routing during a controlled failover.
D:Provisioned Aurora suits sustained predictable throughput and explicit instance sizing. Aurora Global Database does not behave like an automatically conflict-free global multiwriter SQL database.
Question 554
An Aurora cluster must add high-read capacity but not raise writer instance size. What change helps?
- Provision eligible replicas in other AZs for fast DB instance failover.
- Use Aurora Serverless v2 with appropriate minimum and maximum ACU configuration.
- Add reader instances and direct query traffic through the reader endpoint.
- Choose an appropriate relational engine such as Aurora PostgreSQL-compatible when SQL semantics are mandatory.
Explanation
Correct Answer
C:Aurora Replicas share cluster storage while providing read compute scale. Measure writer versus reader CPU utilization.
Incorrect Answers
A:Resilient storage does not by itself provide an alternate running DB compute instance. Add reader instances and direct query traffic through the reader endpoint. Measure writer versus reader CPU utilization.
B:Aurora Serverless v2 scales supported database compute in response to changing demand. Add reader instances and direct query traffic through the reader endpoint. Measure writer versus reader CPU utilization.
D:Database type must match transaction, join and query behavior, not elasticity alone. Aurora Replicas share cluster storage while providing read compute scale.
Question 555
A database has latency spikes while scaling Serverless v2 from a tiny minimum during sudden load. What control should be reviewed?
- Use Aurora Serverless v2 with appropriate minimum and maximum ACU configuration.
- Choose an appropriate relational engine such as Aurora PostgreSQL-compatible when SQL semantics are mandatory.
- Use appropriately provisioned Aurora instances with replicas and capacity planning.
- Set a realistic minimum ACU floor based on expected cold-peak behavior.
Explanation
Correct Answer
D:Serverless minimum capacity affects readiness for abrupt workload changes and cost. Benchmark p95 query latency from the configured floor.
Incorrect Answers
A:Aurora Serverless v2 scales supported database compute in response to changing demand. Set a realistic minimum ACU floor based on expected cold-peak behavior. Benchmark p95 query latency from the configured floor.
B:Database type must match transaction, join and query behavior, not elasticity alone. Set a realistic minimum ACU floor based on expected cold-peak behavior. Benchmark p95 query latency from the configured floor.
C:Provisioned Aurora suits sustained predictable throughput and explicit instance sizing. Set a realistic minimum ACU floor based on expected cold-peak behavior. Benchmark p95 query latency from the configured floor.
Question 556
A high-availability Aurora service has only one database instance even though storage is replicated across AZs. What must be added?
- Provision eligible replicas in other AZs for fast DB instance failover.
- Add reader instances and direct query traffic through the reader endpoint.
- Use appropriately provisioned Aurora instances with replicas and capacity planning.
- Choose an appropriate relational engine such as Aurora PostgreSQL-compatible when SQL semantics are mandatory.
Explanation
Correct Answer
A:Resilient storage does not by itself provide an alternate running DB compute instance. Fail the writer and measure recovery time.
Incorrect Answers
B:Aurora Replicas share cluster storage while providing read compute scale. Provision eligible replicas in other AZs for fast DB instance failover. Fail the writer and measure recovery time.
C:Provisioned Aurora suits sustained predictable throughput and explicit instance sizing. Provision eligible replicas in other AZs for fast DB instance failover. Fail the writer and measure recovery time.
D:Database type must match transaction, join and query behavior, not elasticity alone. Resilient storage does not by itself provide an alternate running DB compute instance.
Question 557
A relational database repeatedly executes expensive identical catalogue queries and could tolerate short stale intervals. Which cache helps?
- Use ElastiCache for Valkey or Redis OSS with supported Multi-AZ failover.
- Use Amazon ElastiCache with suitable TTL and invalidation.
- Persist source-of-truth data in an appropriate durable database or storage system.
- Evaluate DynamoDB Accelerator (DAX) and its compatible request patterns.
Explanation
Correct Answer
B:A managed in-memory cache offloads repetitive reads from the database. Measure hit ratio and origin query reduction.
Incorrect Answers
A:Managed Redis-compatible caches offer replicas and automatic failover options. Use Amazon ElastiCache with suitable TTL and invalidation. Measure hit ratio and origin query reduction.
C:In-memory caches are not a universal replacement for governed durable records. Use Amazon ElastiCache with suitable TTL and invalidation. Measure hit ratio and origin query reduction.
D:DAX adds a read cache in front of DynamoDB with supported consistency constraints. Use Amazon ElastiCache with suitable TTL and invalidation. Measure hit ratio and origin query reduction.
Question 558
A DynamoDB workload needs a compatible cache for eventually consistent item reads with minimal application rewrite. Which option fits?
- Use Amazon ElastiCache with suitable TTL and invalidation.
- Evaluate DynamoDB Accelerator (DAX) and its compatible request patterns.
- Use ElastiCache for Valkey or Redis OSS with supported Multi-AZ failover.
- Distribute workload writes using a higher-cardinality partition key or controlled write sharding.
Explanation
Correct Answer
B:DAX adds a read cache in front of DynamoDB with supported consistency constraints. Benchmark cache-hit latency and newly written data visibility.
Incorrect Answers
A:A managed in-memory cache offloads repetitive reads from the database. Evaluate DynamoDB Accelerator (DAX) and its compatible request patterns. Benchmark cache-hit latency and newly written data visibility.
C:Managed Redis-compatible caches offer replicas and automatic failover options. Evaluate DynamoDB Accelerator (DAX) and its compatible request patterns. Benchmark cache-hit latency and newly written data visibility.
D:Skewed partition keys create hot partitions even when table capacity is available. DAX adds a read cache in front of DynamoDB with supported consistency constraints.
Question 559
A user session store uses Redis-compatible commands and needs high availability across AZs. Which managed option fits?
- Evaluate DynamoDB Accelerator (DAX) and its compatible request patterns.
- Persist source-of-truth data in an appropriate durable database or storage system.
- Use ElastiCache for Valkey or Redis OSS with supported Multi-AZ failover.
- Distribute workload writes using a higher-cardinality partition key or controlled write sharding.
Explanation
Correct Answer
C:Managed Redis-compatible caches offer replicas and automatic failover options. Simulate primary failover and inspect session behavior.
Incorrect Answers
A:DAX adds a read cache in front of DynamoDB with supported consistency constraints. Use ElastiCache for Valkey or Redis OSS with supported Multi-AZ failover. Simulate primary failover and inspect session behavior.
B:In-memory caches are not a universal replacement for governed durable records. Use ElastiCache for Valkey or Redis OSS with supported Multi-AZ failover. Simulate primary failover and inspect session behavior.
D:Skewed partition keys create hot partitions even when table capacity is available. Managed Redis-compatible caches offer replicas and automatic failover options.
Question 560
A team uses ElastiCache for critical persistent records without any durable backing store or recovery. What architectural concern must be addressed?
- Evaluate DynamoDB Accelerator (DAX) and its compatible request patterns.
- Distribute workload writes using a higher-cardinality partition key or controlled write sharding.
- Persist source-of-truth data in an appropriate durable database or storage system.
- Use Amazon ElastiCache with suitable TTL and invalidation.
Explanation
Correct Answer
C:In-memory caches are not a universal replacement for governed durable records. Flush the cache and validate application data recovery.
Incorrect Answers
A:DAX adds a read cache in front of DynamoDB with supported consistency constraints. Persist source-of-truth data in an appropriate durable database or storage system. Flush the cache and validate application data recovery.
B:Skewed partition keys create hot partitions even when table capacity is available. In-memory caches are not a universal replacement for governed durable records.
D:A managed in-memory cache offloads repetitive reads from the database. Persist source-of-truth data in an appropriate durable database or storage system. Flush the cache and validate application data recovery.