DOP-C02 SDLC Automation Practice Test 2 — 15 Questions

Question 1

A company uses AWS CodeCommit as a source repository and wants to enforce that all commits are signed using GPG keys. The DevOps team configures a pre-receive hook in CodeCommit to validate commit signatures. However, the hook rejects all commits even when valid GPG signatures are present. What is the most likely cause?

Accepted Answer

CodeCommit does not support pre-receive hooks.. AWS CodeCommit does not support pre-receive hooks. Pre-receive hooks are a feature of self-managed Git repositories (e.g., GitHub Enterprise, GitLab, or on-premises Git servers) that run on the server before accepting a push. CodeCommit uses IAM policies and repository-level settings (such as requiring signed commits via the 'git push --signed' flag) to enforce commit signing, not server-side hooks. Therefore, any attempt to configure a pre-receive hook in CodeCommit will fail, causing all commits to be rejected.

Answer

The GPG key is not registered with the IAM user's profile.

Answer

The hook script has a syntax error.

Answer

The repository is not configured to require signed commits.

Question 2

A DevOps team is designing a deployment pipeline for a microservices application on Amazon ECS using AWS CodePipeline. They want to implement a canary deployment strategy where a small percentage of traffic is routed to the new version before fully promoting it. Which AWS service or feature should they use to achieve this?

Accepted Answer

AWS CodeDeploy with ECS blue/green deployment. AWS CodeDeploy with ECS blue/green deployment is the correct choice because it natively supports canary traffic shifting for Amazon ECS services. When integrated with AWS CodePipeline, CodeDeploy can route a small percentage of traffic (e.g., 10%) to the new task set, monitor it with CloudWatch alarms, and then automatically shift the remaining traffic after a specified interval. This is the only option that directly provides the canary deployment lifecycle within the ECS and CodePipeline context.

Answer

Amazon ECS Service Auto Scaling

Answer

Amazon Route 53 weighted routing

Answer

AWS App Mesh with traffic shifting

Question 3

A company uses AWS CloudFormation to manage infrastructure. They need to implement a CI/CD pipeline that automatically updates CloudFormation stacks when changes are pushed to a CodeCommit repository. The pipeline must use change sets to review changes before execution. Which pipeline configuration meets these requirements?

Accepted Answer

Use a CloudFormation action with action mode 'CHANGE_SET_REPLACEMENT' and then a separate action with mode 'CHANGE_SET_EXECUTE' after an approval step.. Option B is correct because CodePipeline's CloudFormation deployment action supports a 'CHANGE_SET_REPLACEMENT' mode that creates or replaces a change set without executing it, followed by a 'CHANGE_SET_EXECUTE' action that applies the change set after an approval step. This two-step approach allows teams to review infrastructure changes before they are applied, meeting the requirement to use change sets for review before execution.

Answer

Use a CloudFormation action in CodePipeline with action mode 'CREATE_UPDATE' and include a manual approval step before the action.

Answer

Use an AWS Lambda function to create a change set and trigger a manual approval via SNS.

Answer

Use a CloudFormation action with action mode 'CREATE_UPDATE' and set the 'Review' flag to true.

Question 4

Which of the following are valid strategies for implementing continuous integration in AWS? (Choose two.)

Accepted Answer

Configure AWS CodeBuild to automatically run tests when a pull request is created in CodeCommit.. Option A is correct because AWS CodeBuild can be configured to automatically run tests when a pull request is created in CodeCommit using a webhook or event rule. This enables continuous integration by validating code changes before merging, ensuring that only tested code is integrated into the main branch.

Answer

Set up AWS CodeDeploy to trigger a build every time a commit is pushed to a repository.

Answer

Use AWS CloudFormation to create a stack that runs tests every time a new commit is pushed.

Question 5

A DevOps engineer is designing a deployment pipeline for a serverless application using AWS SAM. The pipeline must include the following stages: source, build, deploy to a development environment, run integration tests, and promote to production after manual approval. Which AWS services and features should be used to implement this pipeline? (Choose two.)

Accepted Answer

AWS CodePipeline to orchestrate the pipeline stages.. AWS CodePipeline is the correct service for orchestrating the pipeline stages because it provides native support for defining source, build, deploy, test, and manual approval stages in a sequential workflow. It integrates directly with AWS SAM and can trigger builds and deployments based on source code changes, making it the ideal orchestrator for this multi-stage pipeline.

Answer

AWS CodeDeploy for deploying the SAM application.

Answer

AWS CodeCommit to build the SAM application.

Question 6

A company uses AWS CodePipeline with Amazon S3 as the source stage. The pipeline triggers on object creation events in the S3 bucket. The development team notices that the pipeline does not trigger when multiple files are uploaded simultaneously. What is the most likely cause?

Accepted Answer

The S3 event notification filter is set to only include objects with a specific prefix or suffix that does not match the uploaded files.. Option B is correct because Amazon S3 event notifications can be filtered by prefix and suffix. If the filter is configured to only match objects with a specific prefix or suffix (e.g., `images/` or `.zip`), and the uploaded files do not match that filter, the event notification will not be sent to CodePipeline, causing the pipeline not to trigger. This is the most likely cause when the pipeline fails to trigger on simultaneous uploads, as the filter configuration is a common misconfiguration.

Answer

Amazon S3 event notifications are not guaranteed to be delivered for bulk operations.

Answer

CodePipeline does not support triggering from S3 event notifications when multiple files are uploaded simultaneously.

Answer

The S3 bucket versioning is not enabled, causing events to be lost.

Question 7

A DevOps engineer is designing a CI/CD pipeline using AWS CodePipeline. The source stage is AWS CodeCommit, and the build stage uses AWS CodeBuild. The pipeline must only trigger on changes to the main branch. However, the engineer notices that the pipeline is also triggering on changes to feature branches that are merged via pull requests. What configuration change should the engineer make to ensure the pipeline only triggers on direct commits to the main branch?

Accepted Answer

Add a branch filter in the CloudWatch Events rule that triggers the pipeline, specifying only the main branch.. Option B is correct because AWS CodePipeline pipelines are triggered by CloudWatch Events rules that monitor CodeCommit repository events. By default, the rule may trigger on all branch changes. Adding a branch filter in the CloudWatch Events rule that specifies only the main branch ensures that only direct commits to main trigger the pipeline, ignoring feature branch merges.

Answer

Configure the CodeCommit repository to disable events for all branches except main.

Answer

Modify the pipeline's source stage to use a branch name filter, which will ignore events from other branches.

Answer

Use a Lambda function as a source action to check the branch before starting the build.

Question 8

A company uses AWS CodeDeploy for deploying applications to an Auto Scaling group of Amazon EC2 instances. The deployment is failing with the error 'The overall deployment failed because too many individual instances failed deployment, too few healthy instances are available, or some instances in your deployment group are experiencing problems.' Which two actions should the DevOps engineer take to troubleshoot and resolve the issue? (Choose two.)

Accepted Answer

Check the CodeDeploy agent logs on the failed instances to identify script errors or missing dependencies.. Option A is correct because the CodeDeploy agent logs on each EC2 instance contain detailed error messages about script failures, missing dependencies, or permission issues that cause the deployment to fail. Checking these logs is the first step in diagnosing why individual instances are failing, as the agent executes the AppSpec lifecycle hooks and reports back to the CodeDeploy service.

Answer

Increase the size of the Auto Scaling group to ensure more instances are available.

Answer

Change the deployment configuration to 'CodeDeployDefault.AllAtOnce' to bypass the error.

Answer

Redeploy the application using a different revision.

Question 9

A DevOps engineer is managing a CI/CD pipeline using AWS CodePipeline with multiple stages: Source (CodeCommit), Build (CodeBuild), Test (CodeBuild), and Deploy (CodeDeploy). The engineer wants to add manual approval steps before the Test and Deploy stages. Additionally, the pipeline should automatically roll back the deployment if the Deploy stage fails. Which two actions should the engineer take to implement these requirements? (Choose two.)

Accepted Answer

Insert a new stage between Build and Test, and add an Approval action to that stage.. Option B is correct because manual approval actions in AWS CodePipeline must be added as a separate stage, not within an existing stage. By inserting a new stage between Build and Test and adding an Approval action, the pipeline pauses before the Test stage, allowing manual review. Option C is correct because CodeDeploy deployment groups support automatic rollback on deployment failure, which can be enabled in the deployment group configuration to revert to the last known good revision.

Answer

Add an Approval action in the Test stage before the Test build action.

Answer

Add a Lambda function in the pipeline that triggers a rollback if the Deploy stage fails.

Answer

Configure the pipeline's Deploy stage to have a 'Rollback' action that runs on failure.

Question 10

Match each AWS service or feature to its correct description in the context of SDLC automation. Drag and drop the items on the left to the matching descriptions on the right.

Answer

AWS CodeCommit

Answer

AWS CodeBuild

Answer

AWS CodeDeploy

Answer

AWS CodePipeline

Answer

AWS CloudFormation

Answer

Amazon EventBridge

Question 11

Drag and drop the steps to configure an AWS Elastic Load Balancer (ALB) with HTTPS listeners and target groups.

Question 12

Match each AWS deployment strategy to its description.

Question 13

A company uses AWS CodePipeline to deploy a web application to an Elastic Beanstalk environment. The pipeline has a source stage from CodeCommit, a build stage using CodeBuild, and a deploy stage to Elastic Beanstalk. Recently, deployments started failing with an error: 'The deployment failed because the Elastic Beanstalk environment is in an UPDATE_ROLLBACK_IN_PROGRESS state.' What is the MOST likely cause?

Accepted Answer

A previous deployment failed and triggered an automatic rollback, leaving the environment in an unstable state. Option B is correct because a failed previous deployment can leave the environment in a rolling back state, preventing subsequent deployments. Option A is wrong because CodeCommit authentication issues would cause the source stage to fail, not the deploy stage. Option C is wrong because build spec errors would cause the build stage to fail. Option D is wrong because CloudWatch alarms do not block deployments.

Answer

The buildspec.yml file contains an invalid command that prevents artifact generation

Answer

A CloudWatch alarm is blocking the deployment due to high error rates

Answer

Insufficient IAM permissions for CodePipeline to pull source code from CodeCommit

Question 14

A DevOps engineer is designing a CI/CD pipeline for a microservices application running on Amazon ECS with Fargate. The team wants to use a blue/green deployment strategy to minimize downtime. Which combination of AWS services and configurations should be used to implement this?

Accepted Answer

Use CodeDeploy with an ECS compute platform and an Application Load Balancer. Option D is correct because CodeDeploy with an ECS compute platform natively supports blue/green deployments for ECS services by orchestrating traffic shifting between two target groups behind an Application Load Balancer. This approach minimizes downtime by gradually routing traffic from the 'blue' (current) task set to the 'green' (new) task set, with built-in rollback capabilities and lifecycle hooks for validation.

Answer

Use Amazon ECS service with a rolling update deployment controller

Answer

Create two separate ECS services and use Route 53 weighted routing to shift traffic

Answer

Use AWS CloudFormation with a custom resource to swap target group weights

Question 15

A company uses AWS CodeBuild to run unit tests and package a Java application. The build process takes 15 minutes. The team wants to reduce build time by caching dependencies. Which approach should the engineer recommend?

Accepted Answer

Configure CodeBuild to use Amazon S3 for cache storage and specify the cache directory in buildspec.yml. Option D is correct because CodeBuild natively supports Amazon S3 for cache storage, allowing you to persist dependency directories across builds. By specifying the cache type as S3 and the path to the dependency cache (e.g., /root/.m2 for Maven) in the buildspec.yml, subsequent builds can reuse previously downloaded dependencies, significantly reducing build time without additional infrastructure.

Answer

Store the compiled dependencies in a separate CodeCommit repository and clone it during the build

Answer

Mount an Amazon EFS file system to the build container and persist the cache across builds

Answer

Use an Application Load Balancer in front of a private artifact repository