nerdexam
Amazon

DOP-C02 · Question #249

A company wants to decrease the time it takes to develop new features. The company uses AWS CodeBuild and AWS CodeDeploy to build and deploy its applications. The company uses AWS CodePipeline to…

The correct answer is B. Program an AWS Lambda function that creates Amazon CloudWatch custom metrics with. Explanation Option B is correct because AWS CodePipeline natively integrates with Amazon CloudWatch metrics, and using a Lambda function that creates CloudWatch custom metrics leveraging CodePipeline's built-in execution state change events (via Amazon EventBridge) provides the…

Submitted by naveen.iyer· Mar 6, 2026Monitoring and Logging

Question

A company wants to decrease the time it takes to develop new features. The company uses AWS CodeBuild and AWS CodeDeploy to build and deploy its applications. The company uses AWS CodePipeline to deploy each microservice with its own CI/CD pipeline. The company needs more visibility into the average time between the release of new features and the average time to recover after a failed deployment. Which solution will provide this visibility with the LEAST configuration effort?

Options

  • AProgram an AWS Lambda function that creates Amazon CloudWatch custom metrics with
  • BProgram an AWS Lambda function that creates Amazon CloudWatch custom metrics with
  • CProgram an AWS Lambda function that writes information about successful runs and failed runs
  • DProgram an AWS Lambda function that writes information about successful runs and failed runs

How the community answered

(39 responses)
  • A
    18% (7)
  • B
    67% (26)
  • C
    10% (4)
  • D
    5% (2)

Explanation

Explanation

Option B is correct because AWS CodePipeline natively integrates with Amazon CloudWatch metrics, and using a Lambda function that creates CloudWatch custom metrics leveraging CodePipeline's built-in execution state change events (via Amazon EventBridge) provides the least configuration effort - specifically, it can track lead time for changes (time from commit to deployment) and mean time to recovery (MTTR) using existing pipeline data without additional tooling. The key differentiator for B over A is that B uses CodePipeline execution events as the data source, which are already available natively, requiring minimal setup. Options C and D are incorrect because writing information to an external store (such as a database or S3) adds unnecessary complexity and additional configuration steps - querying and visualizing that data requires extra services compared to CloudWatch's built-in dashboards and alarms. The distinction between C and D likely involves where the data is stored, but both require more configuration effort than leveraging CloudWatch metrics directly.

Memory Tip: When a question asks for "least configuration effort" with CI/CD visibility metrics, think CloudWatch + EventBridge + CodePipeline events - they're already connected out of the box. If the answer involves writing to a separate data store, it's almost always the more complex option.

Topics

#DORA Metrics#CI/CD Monitoring#Event-driven Architecture#CloudWatch Custom Metrics

Community Discussion

No community discussion yet for this question.

Full DOP-C02 Practice