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.

• ✗

  Amazon Inspector

  Why it's wrong here

  Inspector performs vulnerability assessments of workloads, identifying software flaws and network exposure; it does not track utilisation metrics or trigger threshold alarms. It is the right service for continuous security scanning, whereas CPU monitoring with sustained-period alerting requires CloudWatch metrics and alarms.

• ✗

  AWS Config

  Why it's wrong here

  AWS Config records resource configuration changes and evaluates compliance rules; it does not ingest CloudWatch metric data or trigger threshold alarms. It is tempting because Config can flag non-compliant resources, which suits auditing or configuration drift scenarios, but CPU utilisation over 10 minutes requires CloudWatch alarms.

• ✓

  Amazon CloudWatch Alarms

  Why this is correct

  CloudWatch Alarms evaluates metric thresholds over defined periods and triggers actions when breached. Setting a CPUUtilization alarm above 80% with a ten-minute evaluation period matches the stem's duration and threshold constraints exactly, which raw metrics or dashboards alone cannot enforce.

• ✗

  AWS CloudTrail

  Why it's wrong here

  CloudTrail logs API activity and management events for auditing, not performance metrics, so it cannot detect sustained CPU utilisation above 80%. It is tempting because CloudTrail records account activity, which suits investigating who changed a resource, but metric threshold alerting belongs to CloudWatch.