CLF-C02 Cloud Technology and Services 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.

• ✗

  It automatically scales the database read capacity to handle traffic spikes.

  Why it's wrong here

  Multi-AZ does not modify database capacity or add read capacity in any way. The standby instance is passive and is never used to serve SELECT statements or other read traffic; it exists purely for failover. Scaling read workload is accomplished via read replicas or Aurora Auto Scaling, so this option confuses high availability with performance elasticity.

  When this WOULD be correct

  This would be correct for a question about Amazon RDS read replicas, e.g., 'Which RDS feature automatically scales read capacity for traffic spikes?'

• ✓

  It automatically fails over to a standby instance in a different Availability Zone if the primary instance fails.

  Why this is correct

  Multi-AZ deployments replicate data synchronously to a standby instance in a different Availability Zone. Should the primary instance fail, Amazon RDS automatically promotes the standby, typically within 60–120 seconds, and the endpoint remains unchanged. This is an availability feature only; it does not scale reads or improve performance.

• ✗

  It creates read replicas in multiple Regions to reduce latency for global users.

  Why it's wrong here

  Multi-AZ keeps a synchronous standby in a different Availability Zone within the same region, never in multiple regions. Cross-region read replicas are a separate feature designed for reducing latency for global users and for disaster recovery. This option describes that replica feature, which is unrelated to the high-availability behavior of a Multi-AZ deployment.

  When this WOULD be correct

  This option would be correct for a question asking: 'Which configuration improves read performance for globally distributed users?' or 'What is a benefit of Amazon RDS read replicas in multiple Regions?'

• ✗

  It encrypts data at rest using AWS KMS without any additional configuration.

  Why it's wrong here

  Encryption at rest using AWS KMS is an independent feature that must be explicitly enabled when the DB instance is provisioned; Multi-AZ does not turn it on automatically. A Multi-AZ deployment can be completely unencrypted, and a single-instance database can be encrypted, proving these are orthogonal choices. This answer incorrectly attributes a security capability to an availability feature.

  When this WOULD be correct

  This option would be correct for a question asking: 'Which feature of Amazon RDS for MySQL ensures data is encrypted at rest using AWS KMS with minimal configuration?' — if the question specifies that encryption was enabled at launch, the statement could be true for that specific scenario.

Option-by-option analysis

Why each answer is right or wrong

Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The CLF-C02 exam frequently reuses these exact scenarios with slightly different constraints.

Analysis generated from the official CLF-C02blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”