SAP-C02 Continuous Improvement for Existing 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.

• ✗

  AWS Config

  Why it's wrong here

  AWS Config records resource configuration changes and evaluates compliance against rules; it does not aggregate operational metrics or log streams. It is tempting because it centralises AWS account governance data, and it would be correct for detecting configuration drift or auditing resource state, not for the observability the stem requires.

• ✗

  Amazon Inspector

  Why it's wrong here

  Amazon Inspector performs automated vulnerability scanning of EC2 instances, container images and Lambda functions; it does not aggregate operational metrics or logs. It is tempting for security posture management, but centralised metrics and log analysis across microservices requires Amazon CloudWatch.

• ✓

  Amazon CloudWatch

  Why this is correct

  Amazon CloudWatch aggregates metrics, logs and traces from every microservice into one place, with Logs Insights and dashboards for analysis. This centralised visibility underpins the continuous improvement process the stem requires, unlike per-service tooling that would fragment operational data.

• ✗

  AWS X-Ray

  Why it's wrong here

  AWS X-Ray traces requests through distributed services to build service maps and latency profiles; it does not centralise operational metrics and logs across all microservices. It is tempting because it targets microservice debugging, and it would be correct for pinpointing bottlenecks in a single request path.

Go deeper

Related to this question