DOP-C02 SDLC Automation Practice Test 5 — 15 Questions

Question 1

A development team uses AWS CodePipeline to orchestrate builds and deployments. They want to automatically deploy to a staging environment only if a manual approval step is granted. Which configuration should they use?

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

Add an approval action in the pipeline stage before the deploy action.. AWS CodePipeline supports a manual approval action that pauses the pipeline at a specified stage until an authorized user approves or rejects the deployment. By placing the approval action in the stage before the deploy action, the pipeline will only proceed to the staging deployment after the manual approval is granted, satisfying the requirement exactly.

Answer

Use a Lambda function to check a parameter in Parameter Store.

Answer

Configure a CloudWatch Events rule to trigger deployment after a manual event.

Answer

Set the deploy action to manual invocation only.

Question 2

A company uses AWS CodeCommit for source control. Developers frequently push large binary files (e.g., compiled binaries, datasets) to the repository, causing repository size to grow and clone operations to become slow. What is the BEST approach to manage this?

Accepted Answer

Enable Git LFS in CodeCommit and configure the large files to use LFS.. AWS CodeCommit supports Git Large File Storage (LFS), which replaces large files in the repository with text pointers while storing the actual binary content in a separate hosted storage backend. This keeps the repository lightweight, speeds up clone and fetch operations, and avoids hitting the default repository size limits. Enabling Git LFS is the recommended and best practice for managing large binary files in CodeCommit.

Answer

Use S3 as the source in CodePipeline and skip CodeCommit for binaries.

Answer

Store binaries in a separate CodeCommit repository.

Answer

Increase the repository size limit by requesting a quota increase.

Question 3

A team uses AWS CodeDeploy to deploy an application to an Auto Scaling group. The deployment fails with the error: 'The overall deployment failed because too many individual instances failed deployment.' The instances are healthy and can connect to the CodeDeploy service. What is the most likely cause?

Accepted Answer

The appspec.yml file or lifecycle event scripts have errors.. The error 'too many individual instances failed deployment' indicates that the deployment failed on the instances themselves, not at the infrastructure level. Since the instances are healthy and can connect to CodeDeploy, the most likely cause is that the appspec.yml file or the lifecycle event scripts (e.g., hooks like BeforeInstall, AfterInstall) contain errors that cause the deployment to fail on each instance. This is a common issue when scripts have syntax errors, missing dependencies, or incorrect paths.

Answer

The Auto Scaling group launch configuration is incorrect.

Answer

The deployment group is not configured with the correct service role.

Answer

The target revision is not accessible from the instances.

Question 4

A company uses AWS CloudFormation to manage infrastructure. They want to update a stack but need to ensure that critical database resources are not accidentally replaced during the update. What is the BEST way to protect these resources?

Accepted Answer

Define a stack policy that denies updates to the database resources.. A stack policy explicitly defines which resources can be updated or replaced during a stack update. By applying a stack policy that denies update actions on the critical database resources, you prevent accidental replacement or modification without having to remove the resources from the stack. This is the most direct and robust method to protect specific resources during a CloudFormation update operation.

Answer

Use a CreationPolicy on the database resources.

Answer

Use a DeletionPolicy of Retain on the database resources.

Answer

Set an UpdatePolicy with AutoScalingReplacingUpdate.

Question 5

An organization uses AWS CodePipeline with multiple stages: Source, Build, Deploy to Test, Deploy to Prod. They want to implement a canary deployment strategy for the production deployment. Which approach should they use?

Accepted Answer

Use CodeDeploy with a canary deployment configuration in the Deploy to Prod stage.. AWS CodePipeline integrates natively with CodeDeploy, which supports canary deployments by shifting a percentage of traffic to the new revision over a specified time interval (e.g., 10% every 5 minutes). Using CodeDeploy with a canary configuration in the Deploy to Prod stage directly implements the desired canary strategy within the pipeline, leveraging CodeDeploy's built-in traffic shifting and health monitoring.

Answer

Use a Lambda function in CodePipeline to manually adjust weights in Route53.

Answer

Use an Elastic Load Balancer to gradually shift traffic using weighted target groups.

Answer

Use CloudFormation with a canary update policy in the Deploy to Prod stage.

Question 6

A DevOps engineer is troubleshooting a failed build in AWS CodeBuild. The build log shows: 'Error: Cannot find module 'lodash'.' The buildspec.yml file lists 'npm install' as a command. What is the most likely cause?

Accepted Answer

The package.json file is missing or does not include lodash.. The error 'Cannot find module 'lodash'' indicates that the lodash package is not installed. Since the buildspec includes 'npm install', the most likely cause is that the package.json file is missing or does not list lodash as a dependency. Without package.json or with incorrect dependencies, npm install will not install lodash, leading to the error.

Answer

The npm install command is running before the source is downloaded.

Answer

The lodash package is not compatible with the Node.js version.

Answer

The build environment does not have internet access to download packages.

Question 7

A company uses AWS Elastic Beanstalk for deploying web applications. They want to automate deployments whenever a new commit is pushed to the master branch of their CodeCommit repository. Which AWS service should they use to trigger the deployment?

Accepted Answer

AWS CodePipeline. AWS CodePipeline is a fully managed continuous delivery service that can be configured to automatically trigger a deployment pipeline when a new commit is pushed to a CodeCommit repository's master branch. It integrates directly with CodeCommit as a source action and Elastic Beanstalk as a deployment provider, enabling end-to-end automation without custom scripting.

Answer

AWS CloudTrail

Answer

AWS OpsWorks

Answer

Amazon CloudWatch Events

Question 8

A team uses AWS CloudFormation to deploy a stack that includes an Amazon RDS DB instance. During a stack update, they need to modify the DB instance class but want to avoid downtime. Which update policy should they use?

Accepted Answer

Use a WaitCondition to delay the update until maintenance window.. Using a WaitCondition allows the stack update to be delayed until the RDS maintenance window. If the DB instance is in a Multi-AZ deployment, the instance class change occurs during the maintenance window, causing a failover that minimizes downtime. This approach balances the need to modify the instance class while avoiding significant downtime.

Answer

Use a CreationPolicy on the DB instance.

Answer

Use a stack policy to prevent replacement of the DB instance.

Answer

Use an UpdatePolicy with AutoScalingRollingUpdate.

Question 9

Which TWO AWS services can be used as sources in an AWS CodePipeline? (Choose two.)

Accepted Answer

AWS CodeCommit. AWS CodePipeline supports AWS CodeCommit and Amazon S3 as source stages. CodeCommit is a fully managed source control service that integrates natively with CodePipeline, allowing automatic pipeline execution on code changes. Amazon S3 can serve as a source when you upload a source bundle (e.g., a ZIP file) to an S3 bucket, and CodePipeline can poll the bucket for changes or use S3 event notifications to trigger the pipeline.

Answer

AWS Lambda

Answer

AWS CloudFormation

Answer

AWS CodeBuild

Question 10

Which THREE actions can be performed using the AWS CLI for CodeDeploy? (Choose three.)

Accepted Answer

create-deployment. The `create-deployment` command is correct because it is the primary AWS CLI operation used to start a new deployment in CodeDeploy. It triggers the deployment of a revision (application code and configuration) to a specified deployment group, making it a core action for automating SDLC pipelines.

Answer

push-revision

Answer

register-instance

Question 11

Which TWO are valid deployment configurations in AWS CodeDeploy? (Choose two.)

Accepted Answer

AllAtOnce. In AWS CodeDeploy, the valid deployment configurations are predefined traffic-shifting strategies. 'AllAtOnce' is a valid configuration that deploys the new application revision to all instances simultaneously, making it one of the two correct options. 'Canary10Percent5Minutes' is also a valid configuration that shifts 10% of traffic to the new version for 5 minutes before deploying the remainder, making it the second correct option.

Answer

Rolling

Answer

Linear

Answer

BlueGreen

Question 12

Refer to the exhibit. An IAM policy is attached to a user. The user reports that they cannot push to the 'MyRepo' repository. What is the likely reason?

Accepted Answer

The policy does not allow GitPush on the repository's branches.. The IAM policy shown in the exhibit likely includes a condition or resource restriction that limits the `codecommit:GitPush` action to specific branches, or the policy is missing the `codecommit:GitPush` action entirely. Without explicit permission to push to the repository's branches, the user will receive an access denied error when attempting to push changes. AWS CodeCommit uses IAM policies to control Git operations, and `GitPush` must be allowed on the repository ARN (e.g., `arn:aws:codecommit:region:account:MyRepo`) and optionally on specific branch references using conditions.

Answer

The user is not in the correct IAM group.

Answer

The user does not have GitPull permission on the repository.

Answer

The policy must include codecommit:CreateRepository action.

Question 13

Refer to the exhibit. A DevOps engineer runs the AWS CLI command to list deployments for an application. The output shows only 2 deployments, but the team knows there are more. How can the engineer retrieve the remaining deployments?

Accepted Answer

Use the --starting-token parameter with the value 'abc123' from the output.. The AWS CLI for `deploy list-deployments` uses pagination by default, returning only a subset of results (up to the `--max-items` limit, which defaults to 100 or fewer). The output includes a `NextToken` field (shown as `abc123` in the exhibit), which is an opaque token that must be passed to the `--starting-token` parameter in the next command to retrieve the subsequent page of deployments. This is the standard AWS pagination mechanism for listing APIs.

Answer

Increase the --max-items value to a larger number.

Answer

Run the command without --max-items to get all deployments.

Answer

Use the --no-paginate option.

Question 14

A company uses AWS CodePipeline with a multi-branch strategy. Developers push to feature branches, which should trigger a pipeline that runs unit tests and then deploys to a staging environment. However, the pipeline only triggers on the main branch. What should be done to enable pipeline execution for feature branches?

Accepted Answer

Update the source stage to use 'Webhook' as the change detection method and specify a branch pattern.. AWS CodePipeline can use a webhook (e.g., from GitHub or CodeCommit) to detect changes on any branch. By configuring the source stage with 'Webhook' as the change detection method and specifying a branch pattern (e.g., 'feature/*'), the pipeline will automatically trigger on pushes to matching feature branches, not just the main branch.

Answer

Change the source provider from Amazon S3 to AWS CodeCommit.

Answer

Increase the polling frequency in the source stage to detect new branches.

Answer

Create a separate pipeline for each feature branch.

Question 15

A DevOps team is designing a CI/CD pipeline for a microservices application. Each service is stored in a separate repository. The team wants to build and test only the services that changed in a given commit. Which AWS solution is MOST efficient and cost-effective?

Accepted Answer

Use AWS CodeBuild with a webhook that triggers builds only for repositories where files changed, using buildspec filters.. AWS CodeBuild webhooks can be configured with buildspec filter patterns (e.g., using `git diff` or path-based globs) to trigger builds only for repositories where files changed. This avoids unnecessary builds for unchanged services, making it both efficient and cost-effective by minimizing compute time and resource usage.

Answer

Use AWS CodeCommit triggers with Amazon SNS to send notifications and then manually trigger builds.

Answer

Use AWS CodePipeline with a single pipeline that builds all services on every commit.

Answer

Use Amazon EventBridge to detect repository changes and trigger AWS Lambda functions that determine which services changed.