DOP-C02 Question #109: Real Exam Question with Answer & Explanation

Question

A business has an application that consists of five independent AWS Lambda functions. The DevOps engineer has built a CI/CD pipeline using AWS CodePipeline and AWS CodeBuild that builds, tests, packages, and deploys each Lambda function in sequence. The pipeline uses an Amazon EventBridge rule to ensure the pipeline starts as quickly as possible after a change is made to the application source code. After working with the pipeline for a few months, the DevOps engineer has noticed the pipeline takes too long to complete. What should the DevOps engineer implement to BEST improve the speed of the pipeline?

Options

• AModify the CodeBuild projects within the pipeline to use a compute type with more available network
• BCreate a custom CodeBuild execution environment that includes a symmetric multiprocessing
• CModify the CodePipeline configuration to run actions for each Lambda function in parallel by specifying
• DModify each CodeBuild project to run within a VPC and use dedicated instances to increase

Explanation

Explanation

Option C is correct because CodePipeline supports running actions in parallel by assigning them to the same stage with the same run order, meaning all five Lambda functions can be built, tested, and deployed simultaneously rather than sequentially - directly addressing the root cause of the slow pipeline. Option A is incorrect because increasing network bandwidth in CodeBuild won't meaningfully speed up a pipeline whose bottleneck is sequential execution of five independent functions. Option B is incorrect because a symmetric multiprocessing environment optimizes single-build CPU performance, not the overall pipeline flow across multiple independent deployments. Option D is incorrect because running CodeBuild within a VPC with dedicated instances adds network complexity and cost without solving the fundamental sequential processing problem.

🧠 Memory Tip: Think of it like cooking - if five dishes are independent, you don't cook them one after another; you use parallel burners. In CodePipeline, parallel actions = same stage, same run order. When you see "independent" components taking "too long," always think parallelism first.

No community discussion yet for this question.