DOP-C02 SDLC Automation Practice Test 21 — 15 Questions

Question 1

The exhibit shows the output of the AWS CLI command 'batch-get-builds' for a CodeBuild build. The build failed. What is the most likely cause of the failure?

Accepted Answer

The S3 bucket 'my-bucket' does not exist or the build project lacks permissions to access it.. The `batch-get-builds` output shows a failure in the DOWNLOAD_SOURCE phase, with an error indicating that the build could not access the S3 bucket `my-bucket`. The error details, such as 'Access Denied' or 'NoSuchBucket', imply that the CodeBuild service role lacks the required `s3:GetObject` permission on the bucket, or the bucket does not exist. This is a common misconfiguration when the source code is stored in an S3 bucket and the build project is not properly configured to retrieve it.

Answer

The source code has compilation errors.

Answer

The buildspec file is malformed.

Answer

The build project does not have sufficient memory.

Question 2

The exhibit shows a CloudFormation stack event. The stack creation failed with 'Resource creation cancelled'. What is the most likely reason for this cancellation?

Accepted Answer

The stack was manually cancelled by a user or an automation script.. The 'Resource creation cancelled' event in a CloudFormation stack creation indicates that the operation was explicitly halted by a user or an automation script (e.g., via the AWS CLI, Console, or SDK). This is distinct from a timeout or permission error, which would produce different error messages such as 'Resource creation timed out' or 'API: cloudformation:CreateStack Access Denied'.

Answer

The stack template contains a syntax error.

Answer

The IAM role used for stack operations lacks permissions.

Answer

A stack creation timeout was reached.

Question 3

An organization uses AWS CodeBuild to compile a Java application. The buildspec.yml includes a pre_build phase that runs unit tests. Recently, the build started failing with 'NoClassDefFoundError' for certain test dependencies, even though the pom.xml includes them. The build environment uses an Amazon Linux 2 Docker image. What is the MOST likely cause?

Accepted Answer

The CodeBuild project has a cache that is corrupted or out of sync. Clear the build cache.. The 'NoClassDefFoundError' for test dependencies that are declared in pom.xml indicates that the required JAR files are missing from the build environment at runtime. A corrupted or out-of-sync build cache in CodeBuild can cause previously downloaded Maven dependencies to be reused incorrectly, leading to missing classes even though the pom.xml specifies them. Clearing the cache forces a fresh download of all dependencies, resolving the mismatch.

Answer

The S3 bucket for artifacts has incorrect permissions. Update the bucket policy.

Answer

The CodeCommit repository is not pulling the latest code. Add a webhook to trigger builds on push.

Answer

The build environment does not have Maven installed. Install Maven in the buildspec.

Question 4

A company uses AWS CloudFormation to manage infrastructure. The DevOps team wants to deploy a stack across multiple accounts using AWS CodePipeline. Which approach is BEST for automating cross-account deployments?

Accepted Answer

Use a single pipeline in the management account with IAM roles that assume cross-account roles.. AWS CodePipeline can assume an IAM role in the target account (via a cross-account role) to perform CloudFormation deployments. This allows a single pipeline in the management account to automate deployments across multiple accounts without manual triggers or separate pipelines, adhering to the principle of least privilege and centralized control.

Answer

Use AWS CloudFormation StackSets to deploy the stack across accounts.

Answer

Create a separate pipeline in each account and trigger them manually.

Answer

Use an S3 bucket with cross-account access and Lambda to invoke CloudFormation.

Question 5

A company uses AWS CodeCommit for source control. Developers report that their local branches are out of sync with the remote repository, and they are unable to push changes because of 'non-fast-forward' errors. What should the developers do to fix this?

Accepted Answer

Pull the latest changes using 'git pull --rebase' and then push.. The 'non-fast-forward' error occurs when the local branch is behind the remote branch, meaning the remote has commits the local doesn't have. Running 'git pull --rebase' fetches the latest remote changes and replays the local commits on top of them, creating a linear history. After this, the local branch is up to date and the push will succeed without needing to force or create a new branch.

Answer

Create a new branch and push that instead.

Answer

Use 'git push --force' to overwrite the remote branch.

Answer

Delete the remote branch and push again.

Question 6

A DevOps team is implementing a CI/CD pipeline using AWS CodePipeline. The pipeline has a Source stage using CodeCommit, a Build stage using CodeBuild, and a Deploy stage using CloudFormation. The team wants to add manual approval before the Deploy stage for production deployments. How should this be configured?

Accepted Answer

Add an Approval stage to the pipeline with SNS topic for notification.. AWS CodePipeline natively supports Approval stages that can be configured to pause the pipeline and send a notification via an SNS topic. The SNS topic can be subscribed to by email, SMS, or other endpoints, allowing a manual approver to review the build output and then approve or reject the transition to the Deploy stage. This directly meets the requirement for a manual approval gate before production deployment without custom code or separate pipelines.

Answer

Configure a CloudWatch event to send an email on build success.

Answer

Use a Lambda function to approve based on build status.

Answer

Create a separate pipeline for production and trigger it manually.

Question 7

A company uses AWS Elastic Beanstalk to deploy a web application. The deployment fails with a '502 Bad Gateway' error. The developer checks the logs and sees that the application is running but returns errors. The environment uses a load balancer. What is the MOST likely cause?

Accepted Answer

The application is not binding to the correct port or is crashing under load.. A 502 Bad Gateway error from an Elastic Beanstalk environment with a load balancer typically indicates that the reverse proxy (nginx or Apache) is unable to communicate with the application process. Since the logs show the application is running but returning errors, the most likely cause is that the application is not binding to the correct port (expected port 8080 by default) or is crashing under load, causing the proxy to receive no valid response and return a 502.

Answer

The application source bundle is missing a required file.

Answer

The security group of the environment does not allow inbound HTTP traffic.

Answer

The environment's environment variables are misconfigured.

Question 8

A DevOps engineer needs to automate the creation of a new AWS CodeCommit repository when a new project starts. The engineer wants to use infrastructure as code. Which service should be used?

Accepted Answer

AWS CloudFormation. AWS CloudFormation is the correct service because it allows you to define and provision AWS infrastructure as code using templates. You can declare an AWS::CodeCommit::Repository resource in a CloudFormation template, which will automatically create the CodeCommit repository when the stack is created, enabling fully automated and repeatable infrastructure deployment.

Answer

AWS CodePipeline

Answer

AWS CodeStar

Answer

AWS CodeBuild

Question 9

An organization uses AWS CodeDeploy for automated deployments to 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 for deployment, or some instances in your deployment group are experiencing problems.' The deployment group has a minimum healthy hosts setting of 75%. The application has 4 instances. What is the MOST likely issue?

Accepted Answer

The deployment failed on 2 instances, leaving only 2 healthy.. With a minimum healthy hosts setting of 75% and 4 instances, at least 3 instances must remain healthy during deployment. If 2 instances fail, only 2 are healthy (50%), which falls below the 75% threshold, causing CodeDeploy to abort the deployment to prevent further impact. This error message directly corresponds to the healthy host count dropping below the configured minimum.

Answer

The AppSpec file references a script that does not exist.

Answer

The IAM instance profile does not have sufficient permissions.

Answer

The CodeDeploy agent is not installed on any of the instances.

Question 10

Which THREE actions should a DevOps team take to ensure a CI/CD pipeline using AWS CodePipeline is secure? (Choose three.)

Accepted Answer

Use AWS KMS to encrypt artifacts in the pipeline.. AWS CodePipeline can use AWS KMS customer-managed keys (CMKs) to encrypt artifacts stored in S3 or other supported stores. This ensures that pipeline artifacts are encrypted at rest and in transit, protecting sensitive data from unauthorized access. By default, CodePipeline uses an AWS-managed key, but using a customer-managed KMS key gives the team full control over encryption, key rotation, and access policies.

Answer

Require multi-factor authentication (MFA) for pipeline executions.

Answer

Enable AWS CloudTrail to log pipeline executions.

Question 11

Which TWO options are valid ways to trigger an AWS CodePipeline execution automatically? (Choose two.)

Accepted Answer

Changes to a CodeCommit repository.. AWS CodePipeline can automatically start a pipeline execution when a change is detected in a CodeCommit repository. This is achieved through CloudWatch Events that monitor the repository for specific events like push to a branch, and then trigger the pipeline. This integration allows for continuous delivery by automatically building and deploying code changes.

Answer

A scheduled CloudWatch Logs metric filter.

Answer

Completion of a CodeDeploy deployment.

Answer

Manual approval action in the pipeline.

Question 12

Which THREE factors should be considered when designing a deployment strategy using AWS CodeDeploy to minimize downtime during updates? (Choose three.)

Accepted Answer

Configure a load balancer to deregister instances before deployment.. Deregistering instances from a load balancer before deployment ensures that traffic is not routed to instances that are being updated, preventing downtime during the deployment process. AWS CodeDeploy integrates with Elastic Load Balancing to automatically deregister instances, wait for in-flight requests to complete, and then register them back after the deployment succeeds.

Answer

Deploy to all instances simultaneously to reduce total time.

Answer

Use the same instance type for all instances.

Question 13

Refer to the exhibit. The above IAM policy is attached to an IAM role used by a CI/CD pipeline. Which action is this policy allowing?

Accepted Answer

Start and view builds for the specified CodeBuild project.. The IAM policy grants `codebuild:StartBuild` and `codebuild:BatchGetBuilds` actions, which allow starting a build and viewing build details respectively. The `Resource` element restricts these permissions to the specific CodeBuild project `arn:aws:codebuild:us-east-1:123456789012:project/my-project`. Therefore, the policy allows starting and viewing builds for that single project, not any project in the account.

Answer

Start builds for any CodeBuild project in the account.

Answer

View details of any build in the account.

Answer

Create and manage CodeBuild projects.

Question 14

Refer to the exhibit. A DevOps engineer ran the above AWS CLI command after a CloudFormation stack update. What does the status 'ROLLBACK_COMPLETE' indicate?

Accepted Answer

The stack update failed and CloudFormation reverted to the previous stack.. The 'ROLLBACK_COMPLETE' status indicates that the CloudFormation stack update operation failed, and CloudFormation automatically reverted the stack to its previous stable state. This is a built-in safety mechanism: if any resource fails to update, CloudFormation triggers a rollback to undo all changes made during the update, ensuring the stack returns to its last known good configuration.

Answer

The stack update is in progress.

Answer

The stack was deleted successfully.

Answer

The stack was created successfully.

Question 15

Refer to the exhibit. The above buildspec.yml is used in AWS CodeBuild. The build is failing during the 'build' phase with a 'FileNotFoundError: setup.py' error. What is the MOST likely cause?

Accepted Answer

The source code does not contain a setup.py file in the root directory.. The error 'FileNotFoundError: setup.py' indicates that the build process is attempting to run a command (likely `python setup.py install` or `pip install -e .`) that requires a `setup.py` file in the root directory of the source code. Since the buildspec.yml does not explicitly override the default build commands, CodeBuild uses the default build command for Python, which expects `setup.py` to be present. Option A is correct because the most likely cause is that the source code repository lacks a `setup.py` file in its root directory, causing the build phase to fail.

Answer

The unit tests in the post_build phase are failing.

Answer

The Python version 3.8 is not supported by CodeBuild.

Answer

The artifacts configuration discarding paths is causing the error.