DOP-C02 SDLC Automation Practice Test 9 — 15 Questions

Question 1

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.. 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 2

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 3

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.. 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 4

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.. 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 5

Which AWS service is a fully managed source control service?

Accepted Answer

AWS CodeCommit. AWS CodeCommit is a fully managed source control service that hosts private Git repositories, providing version control without managing servers. It integrates with IAM for access control and other AWS developer tools. The other services in the list serve different CI/CD pipeline stages.

Answer

AWS CodeBuild

Answer

AWS CodeDeploy

Answer

AWS CodePipeline

Answer

AWS CloudFormation

Answer

Amazon EventBridge

Question 6

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

Accepted Answer

Create target group, Create ALB, Configure HTTPS listener, Register targets, Add redirect rule. First create the target group, then create the ALB, then configure HTTPS listener, then register targets, then add redirect rule.

Answer

Create ALB, Create target group, Configure HTTPS listener, Register targets, Add redirect rule

Answer

Create target group, Create ALB, Register targets, Configure HTTPS listener, Add redirect rule

Answer

Configure HTTPS listener, Create target group, Create ALB, Register targets, Add redirect rule

Question 7

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. The error indicates the Elastic Beanstalk environment is stuck in an UPDATE_ROLLBACK_IN_PROGRESS state, which occurs when a previous deployment failed and Elastic Beanstalk automatically rolled back the changes. This leaves the environment in an unstable state that prevents new deployments until the rollback completes or is manually resolved. CodePipeline cannot proceed because Elastic Beanstalk rejects any new update operations while in this state.

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 8

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. 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 9

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. 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

Question 10

A development team uses AWS CodeCommit as a source control repository. A developer accidentally pushed a commit that contains sensitive information (e.g., AWS access keys) to the main branch. The team wants to remove the sensitive data from the repository history completely. Which action should the engineer take?

Accepted Answer

Use 'git filter-branch' to rewrite the repository history and remove the sensitive file. 'git filter-branch' (or the modern 'git filter-repo') rewrites the repository history by removing or replacing the sensitive file in every commit, effectively purging it from the entire Git history. This is the only native Git method that completely eliminates the sensitive data from all past commits, preventing anyone from retrieving it via 'git log' or by cloning the repository. After rewriting history, a force push to the remote CodeCommit repository is required to overwrite the remote branches.

Answer

Delete the repository and create a new one, then force push the remaining branches

Answer

Use 'git revert' to create a new commit that undoes the changes

Answer

Create a new branch from the commit before the sensitive data was added and merge it to main

Question 11

A company runs a critical application on Amazon EC2 instances behind an Application Load Balancer. The application is deployed using AWS CodeDeploy with an in-place deployment configuration. During a recent deployment, the deployment failed because the new application version caused a health check failure, and CodeDeploy did not automatically roll back. What should the engineer do to ensure automatic rollback on health check failure?

Accepted Answer

Enable automatic rollback in the CodeDeploy deployment group and set up a CloudWatch alarm for the ALB health check. CodeDeploy can automatically roll back a deployment when a CloudWatch alarm, such as one monitoring ALB health check failures, enters the ALARM state. By enabling automatic rollback in the deployment group and associating the CloudWatch alarm, the deployment will revert to the previous version as soon as the health check fails, without manual intervention.

Answer

Set up an EC2 instance lifecycle hook to trigger a rollback script when the instance enters a pending state

Answer

Configure an Amazon SQS queue to monitor health checks and invoke a rollback Lambda function

Answer

Modify the Auto Scaling group to replace unhealthy instances automatically

Question 12

A team uses AWS CloudFormation to manage infrastructure. They want to deploy a stack that creates an S3 bucket and a DynamoDB table. The S3 bucket name must be unique across all AWS accounts. Which CloudFormation intrinsic function should be used to generate a unique bucket name?

Accepted Answer

!Sub 'mybucket-${AWS::AccountId}'. The `!Sub 'mybucket-${AWS::AccountId}'` intrinsic function substitutes the AWS::AccountId pseudo parameter, which is guaranteed to be unique per AWS account. Since S3 bucket names must be globally unique across all AWS accounts, appending the account ID ensures the generated name does not conflict with buckets in other accounts. This approach is a common pattern for creating unique resource names in CloudFormation.

Answer

!Ref 'AWS::StackName'

Answer

!GetAtt S3Bucket.Arn

Answer

!Select [0, !Split ['-', !Ref 'AWS::Region']]

Question 13

A company deploys a serverless application using AWS SAM. The application includes an API Gateway REST API and multiple Lambda functions. The team wants to implement canary deployments for the API to gradually shift traffic to a new version. Which SAM template configuration should be used?

Accepted Answer

Use the CanaryDeployment property on the Serverless::Function resource with a DeploymentPreference. AWS SAM's `CanaryDeployment` property on the `AWS::Serverless::Function` resource, combined with a `DeploymentPreference` of type `Canary10Percent5Minutes`, enables gradual traffic shifting for API Gateway integrations. This configuration automatically creates a Lambda alias, publishes new versions, and shifts a percentage of API traffic to the new version over a specified time window, all without manual intervention.

Answer

Create multiple Lambda function versions and use API Gateway stage variables to switch between them

Answer

Define the Lambda function with AutoPublishAlias: live and set the API Gateway integration to point to the alias

Answer

Use AWS CloudFormation's UpdatePolicy with AutoScalingRollingUpdate

Question 14

A developer is setting up AWS CodeBuild to compile a Go application. The build fails with the error: 'go: command not found'. What is the MOST likely cause?

Accepted Answer

The build environment image does not have the Go runtime installed. The error 'go: command not found' indicates that the Go executable is not available in the build environment's PATH. CodeBuild uses a managed or custom build environment image (e.g., Ubuntu, Amazon Linux 2) to run build commands. If the image does not include the Go runtime, the shell cannot locate the 'go' binary, causing the build to fail. The most direct fix is to select a build environment image that has Go pre-installed or to install Go in the install phase of the buildspec.

Answer

The environment variables in buildspec.yml are incorrectly set

Answer

The build project does not have enough memory to compile Go code

Answer

The CodeBuild service role does not have permission to access the S3 bucket for artifacts

Question 15

Which TWO actions should a DevOps engineer take to implement a CI/CD pipeline that automatically deploys a containerized application to Amazon ECS using AWS CodePipeline and AWS CodeBuild? (Choose TWO.)

Accepted Answer

Use CodeBuild to build the Docker image and push it to Amazon ECR. AWS CodeBuild can be configured to build the Docker image from source code and then push it to Amazon ECR using the `post_build` phase with commands like `docker push`. This is a standard pattern for containerized CI/CD pipelines, as ECR serves as the private registry for storing and versioning container images. Option E is correct because CodePipeline can use Amazon ECR as a source action, which triggers the pipeline automatically when a new image is pushed to the specified repository, enabling continuous deployment to ECS.

Answer

Use AWS CloudFormation to deploy the ECS service

Answer

Use AWS CodeDeploy to deploy the container to ECS with a blue/green deployment

Answer

Store the Docker image in AWS CodeCommit