DVA-C02 Deployment Practice Test 16 — 15 Questions

Question 1

A developer is using AWS CodeDeploy to deploy an application to an Auto Scaling group. The deployment fails during the 'BeforeInstall' lifecycle event. Which file should the developer check to debug the failure?

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

Accepted Answer

appspec.yml. The 'BeforeInstall' lifecycle event in AWS CodeDeploy is a hook defined in the appspec.yml file. This file specifies the deployment lifecycle hooks, including scripts to run before installation. When a deployment fails during this event, the appspec.yml is the primary file to inspect for misconfigured scripts, incorrect permissions, or missing script paths.

Answer

index.js

Answer

taskdef.json

Answer

buildspec.yml

Question 2

A developer is using AWS CodeCommit as a source repository. They want to automatically build and test code whenever a new branch is created. Which AWS service should they use to trigger the pipeline?

Accepted Answer

Amazon CloudWatch Events. Amazon CloudWatch Events (now part of Amazon EventBridge) can capture AWS CodeCommit repository events, such as the creation of a new branch. By setting a rule that matches the 'Reference Created' event type, you can automatically trigger an AWS CodePipeline pipeline execution, enabling continuous integration for new branches.

Answer

Amazon S3 event notification

Answer

Amazon Simple Notification Service (SNS)

Answer

AWS Lambda

Question 3

A company uses AWS CodePipeline to deploy a static website to Amazon S3. The pipeline includes a deploy action that uses AWS CloudFormation to create the S3 bucket and upload files. The developer notices that the deploy action fails intermittently with a 'BucketAlreadyExists' error. What is the most likely cause?

Accepted Answer

The S3 bucket name is already taken by another AWS account.. The 'BucketAlreadyExists' error occurs when an S3 bucket name is globally unique across all AWS accounts. If the bucket name specified in the CloudFormation template has already been claimed by another AWS account, the deployment will fail intermittently if the bucket is deleted and recreated or if the pipeline runs in a different region where the name is taken. This is a common issue when using hardcoded or non-unique bucket names.

Answer

The S3 bucket has versioning enabled.

Answer

The CloudFormation template has incorrect IAM permissions.

Answer

The S3 bucket policy is too restrictive.

Question 4

A company is using AWS CodeBuild to compile a Java application. The build takes a long time because Maven dependencies are downloaded each time. How can the developer reduce build time?

Accepted Answer

Configure a cache in Amazon S3 for the Maven repository.. Configuring an Amazon S3 cache for the Maven repository allows CodeBuild to reuse previously downloaded dependencies across builds, eliminating the need to re-download them each time. This significantly reduces build time by leveraging the local cache stored in S3, which is a best practice for dependency-heavy builds like Java applications with Maven.

Answer

Use a higher compute type for the build project.

Answer

Use a custom AMI with pre-installed dependencies.

Answer

Increase the timeout value for the build.

Question 5

A developer is using AWS CodePipeline with multiple actions in a stage. The pipeline has a build action that produces artifacts, followed by a deploy action. The developer wants to ensure that if the deploy action fails, the pipeline stops and does not continue to the next stage. How can they achieve this?

Accepted Answer

No additional configuration is needed; the pipeline stops on failure by default.. AWS CodePipeline stages are sequential by default: if any action within a stage fails, the entire stage fails and the pipeline stops, preventing execution of subsequent stages. No additional configuration is needed to halt the pipeline on a deploy action failure, as this is the inherent behavior of a pipeline stage with multiple actions.

Answer

Configure the deploy action to 'Abort' on failure.

Answer

Set the runOrder for the deploy action to 'Blocked'.

Answer

Set the pipeline's execution mode to 'PARALLEL'.

Question 6

Which TWO are valid deployment strategies supported by AWS CodeDeploy? (Choose TWO.)

Accepted Answer

In-place deployment. AWS CodeDeploy supports in-place deployments (option B) where the application is updated on the existing instances without provisioning new ones. This is a valid deployment strategy that updates the current fleet by stopping and starting the application, and it is one of the two core strategies explicitly documented by AWS.

Answer

Immutable deployment

Answer

Canary deployment

Answer

All at once deployment

Question 7

Which THREE are best practices for deploying applications with AWS Elastic Beanstalk? (Choose THREE.)

Accepted Answer

Use environment configuration files (.ebextensions) to manage settings.. Ebextensions configuration files allow you to define environment settings, software configurations, and custom resources declaratively, ensuring consistent and repeatable deployments without manual intervention. This aligns with the best practice of infrastructure as code, as Elastic Beanstalk automatically applies these settings during environment creation and updates.

Answer

Manually update EC2 instances in the environment.

Answer

Always use the default Elastic Beanstalk domain for production.

Question 8

A developer created a CloudFormation template to host a static website. After deployment, the website returns 403 Forbidden errors. What is the most likely cause?

Accepted Answer

The bucket policy does not allow public access.. An 'Access Denied' (403 Forbidden) error on an Amazon S3 static website endpoint indicates that the requester does not have permission to access the resource. By default, all new S3 buckets and objects are private. To allow public access to the website's assets, you must add a bucket policy that grants public read permissions (`s3:GetObject`) to anonymous users, and ensure that S3 Block Public Access settings are disabled. If static website hosting were not enabled, the website endpoint would not return a 403 Forbidden error; it would not resolve or would return a 404 error. Therefore, the missing bucket policy is the most likely cause.

Answer

The bucket has versioning enabled, which blocks public access.

Answer

The bucket name is not unique.

Answer

The bucket does not have static website hosting enabled.

Question 9

A company has a production environment using AWS Elastic Beanstalk with a multi-container Docker platform. The application consists of a PHP web server and a Redis cache, each running in separate containers. The deployment uses a rolling update policy with a batch size of 1. Recently, during deployments, some users experience intermittent 502 Bad Gateway errors for about 30 seconds. The errors occur when the old containers are terminated and new containers are not yet ready to serve traffic. The development team wants to eliminate this downtime without increasing the deployment time significantly. The team has access to modify the Elastic Beanstalk environment configuration and the Dockerrun.aws.json file. Which action should the team take to resolve the issue?

Accepted Answer

Configure a health check grace period in the Elastic Beanstalk environment to delay load balancer registration until the containers are healthy.. Configuring a health check grace period allows new containers time to become healthy before the load balancer routes traffic to them, preventing the 502 errors during the transition. Option A is incorrect because increasing the batch size would cause more containers to be replaced simultaneously, potentially increasing downtime. Option C is incorrect because 'All at once' deployment would terminate all old containers before starting new ones, causing full downtime. Option D is incorrect because reducing the health check interval would make the load balancer check more frequently, which could cause premature routing to unhealthy instances and exacerbate the issue.

Answer

Increase the batch size to 2 to reduce the number of deployment cycles.

Answer

Change the deployment policy to 'All at once' to complete the deployment faster.

Answer

Reduce the health check interval on the load balancer to detect healthy instances faster.

Question 10

A developer is deploying a new version of a Lambda function using an AWS CodePipeline pipeline. The deployment fails during the 'Deploy' stage with an error indicating that the function's code is too large. What should the developer do to resolve this issue?

Accepted Answer

Upload the Lambda deployment package to Amazon S3 and reference it from the function. AWS Lambda has a hard limit of 50 MB for direct uploads via the console or API. When a deployment package exceeds this limit, the correct approach is to upload the package to Amazon S3 and configure the Lambda function to reference the S3 object. CodePipeline can then use the S3 location to deploy the function, bypassing the direct upload size restriction.

Answer

Increase the Lambda function's timeout setting

Answer

Use Amazon CloudFront to distribute the Lambda code

Answer

Enable AWS X-Ray tracing on the Lambda function

Question 11

A team uses AWS Elastic Beanstalk to deploy a web application. The application experiences intermittent high latency. The team notices that the environment's Auto Scaling group is not scaling out quickly enough. Which configuration change should the team make to improve scaling responsiveness?

Accepted Answer

Decrease the Auto Scaling group's cooldown period. Decreasing the Auto Scaling group's cooldown period reduces the time that the group waits after a scaling activity before it can launch another instance, thereby improving scaling responsiveness. Option A is incorrect because a lighter health check path does not affect scaling speed—it only affects how quickly unhealthy instances are detected. Option B is incorrect; while detailed CloudWatch metrics provide more granular data, they do not directly reduce the cooldown period. Option C is incorrect because increasing instance size improves per-instance capacity but does not change how quickly the group scales out.

Answer

Modify the Elastic Load Balancer health check path to a lighter endpoint

Answer

Enable detailed CloudWatch metrics for the Auto Scaling group

Answer

Increase the instance type to a larger size

Question 12

A developer is using AWS CodeDeploy to deploy an application to an Auto Scaling group. The deployment fails during the 'BeforeInstall' lifecycle event. Which file should the developer check to debug the failure?

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

Accepted Answer

The script file specified in the appspec.yml for the BeforeInstall hook is not present on the instance. The 'ScriptMissing' error in AWS CodeDeploy indicates that the deployment failed because a script file referenced in the appspec.yml for a lifecycle event (in this case, BeforeInstall) could not be found on the EC2 instance. CodeDeploy expects the script to be present at the specified path after the archive is extracted; if the file is missing or the path is incorrect, the agent reports this error. Option B correctly identifies that the script file is not present on the instance.

Answer

The BeforeInstall lifecycle event is not defined in the appspec.yml

Answer

The CodeDeploy agent on the instance is not running

Answer

The instance does not have the necessary permissions to execute the script

Question 13

A developer is deploying a serverless application using AWS SAM. The application consists of multiple Lambda functions and an API Gateway REST API. The developer needs to ensure that the API Gateway endpoint is created before the Lambda functions are deployed, because the functions need the endpoint URL as an environment variable. How should the developer configure the SAM template?

Accepted Answer

Define the Lambda functions to use the ServerlessRestApi implicit API and reference the API's output in the function's environment variables. AWS SAM automatically creates an implicit API Gateway REST API (logical ID `ServerlessRestApi`) when you define an `AWS::Serverless::Api` or use the `Events` property on a function. You can reference its endpoint URL using the `Fn::Sub` intrinsic function with the `ServerlessRestApi` logical ID, such as `!Sub 'https://${ServerlessRestApi}.execute-api.${AWS::Region}.amazonaws.com/${Stage}'`. This ensures the API Gateway resource is created before the Lambda functions that reference it, as CloudFormation resolves dependencies through intrinsic function references.

Answer

Separate the deployment into two stacks: first deploy API Gateway, then deploy Lambda functions

Answer

Add a DependsOn clause to each Lambda function resource to wait for the API Gateway resource

Answer

Use a custom resource in CloudFormation to create the API Gateway endpoint before Lambda functions

Question 14

A developer is using AWS CodeBuild to compile and package a Java application. The build process takes longer than expected. The developer wants to speed up the build by reusing dependencies that have not changed between builds. Which feature should the developer enable?

Accepted Answer

Enable caching for the CodeBuild project by specifying an S3 bucket for cache storage. AWS CodeBuild caching allows you to persist dependencies (e.g., Maven .m2 repository, Gradle caches) between builds. By specifying an S3 bucket as the cache storage, CodeBuild uploads the cache after a successful build and downloads it at the start of subsequent builds, avoiding re-downloading unchanged dependencies. This significantly reduces build time for Java applications.

Answer

Configure the build project to run builds concurrently

Answer

Enable build artifacts in the CodeBuild project

Answer

Store the build's output artifacts in an S3 bucket

Question 15

A company uses AWS OpsWorks to manage a stack of EC2 instances. The operations team needs to deploy a new configuration file to all instances in a layer. Which approach should the team use to automate this deployment?

Accepted Answer

Add a Chef recipe to the layer's custom cookbooks that copies the configuration file to the instances. The correct answer is B: adding a Chef recipe to the layer's custom cookbooks that copies the configuration file to the instances. AWS OpsWorks Stacks is built on Chef, so configuration management tasks like distributing files to all instances in a layer are performed through recipes executed during lifecycle events (Setup, Configure, Deploy), making this the native and automated approach. Option A is not the OpsWorks-native mechanism and would bypass the stack's Chef-based lifecycle, requiring manual invocation or separate targeting. Option C is incorrect because CloudFormation provisions infrastructure and does not manage in-instance configuration files for an existing OpsWorks stack. Option D is also wrong because CodeDeploy is a separate deployment service not integrated with OpsWorks Stacks' Chef recipe model.

Answer

Use AWS Systems Manager Run Command to execute a script that deploys the file

Answer

Create a new AWS CloudFormation stack to update the instances

Answer

Use AWS CodeDeploy to deploy the configuration file