DVA-C02 Deployment Practice Test 2 — 15 Questions

Question 1

A developer is using AWS Elastic Beanstalk to deploy a web application. The application requires custom configuration, such as setting environment variables for the EC2 instances. Which file should the developer include in the application source bundle under the appropriate directory to achieve this?

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

Accepted Answer

Include a .ebextensions/options.config file.. AWS Elastic Beanstalk uses `.ebextensions` directory with `.config` files (e.g., `options.config`) to define custom configuration, including environment variables for EC2 instances. These YAML or JSON files are processed during environment creation and updates, allowing you to set `option_settings` that override or augment the default platform configuration.

Answer

Include a buildspec.yml file in the root directory.

Answer

Include an appspec.yml file.

Answer

Include a cron.yaml file.

Question 2

A developer is using AWS CloudFormation to deploy a stack with multiple resources. To ensure that a specific EC2 instance is created only after a security group is created, the developer wants to define the dependency. How should the developer achieve this in the CloudFormation template?

Accepted Answer

Use the DependsOn attribute on the EC2 instance resource. When there is no direct relationship or reference between two resources in a CloudFormation template, you must use the `DependsOn` attribute to explicitly define the creation order. If a reference (like `Ref` or `Fn::GetAtt`) already exists between the resources, CloudFormation automatically handles the dependency implicitly, making `DependsOn` unnecessary in those cases.

Answer

Use the Ref function to refer to the security group in the EC2 instance properties

Answer

Use the AWS::NoValue intrinsic function

Answer

Use the Condition attribute on the EC2 instance

Question 3

A developer is deploying an application using AWS Elastic Beanstalk. The application requires a custom Amazon Machine Image (AMI) that includes specific software packages not available in the standard Elastic Beanstalk platform. Which approach should the developer use to ensure the custom AMI is used for all EC2 instances in the environment?

Accepted Answer

Modify the .ebextensions configuration file to specify the custom AMI ID.. AWS Elastic Beanstalk allows you to use a custom AMI with a standard platform. To ensure the custom AMI is used for all EC2 instances in the environment, you can specify the AMI ID in the 'ImageId' option of the 'aws:autoscaling:launchconfiguration' namespace using an .ebextensions configuration file. This is the standard infrastructure-as-code approach for applying a custom AMI.

Answer

Create a custom platform using the Packer tool and specify it in the environment configuration.

Answer

Use the Elastic Beanstalk console to change the AMI ID in the environment configuration after creation.

Answer

Launch a new environment with a different platform version that includes the required software.

Question 4

A developer is deploying an application using AWS Elastic Beanstalk with a Docker platform. The developer wants to minimize downtime during deployments and ensure that the new version is fully tested before routing traffic to it. Which deployment policy should the developer choose?

Accepted Answer

Immutable.. Immutable deployments (Option C) are correct because AWS Elastic Beanstalk deploys the new version to a fresh set of instances in a temporary Auto Scaling group and performs health checks. Only after these instances pass health checks (are 'fully tested') does Elastic Beanstalk route traffic to them and terminate the old instances. This ensures zero downtime and guarantees that no production traffic is routed to the new version until it is verified as healthy.

Answer

All at once.

Answer

Rolling with additional batch.

Answer

Traffic splitting.

Question 5

A developer is deploying a web application using AWS Elastic Beanstalk. The application runs on multiple Amazon EC2 instances behind an Application Load Balancer. The developer wants to deploy a new version with zero downtime and the ability to quickly roll back if issues are discovered. Which deployment policy should the developer choose?

Accepted Answer

Immutable. Immutable deployment is the correct choice because it launches a completely new set of EC2 instances in a temporary Auto Scaling group alongside the existing ones. Once the new instances pass health checks, they are integrated, and the old instances are terminated. This guarantees zero downtime. If the deployment fails at any point during the process, Elastic Beanstalk simply terminates the new temporary Auto Scaling group, resulting in an immediate rollback with zero impact on the active environment.

Answer

All at once

Answer

Rolling

Answer

Rolling with additional batch

Question 6

A developer is deploying a web application on AWS Elastic Beanstalk. The environment must maintain the same number of running instances throughout the deployment to ensure capacity. The developer also wants to minimize downtime. Which deployment policy should be used?

Accepted Answer

Rolling with additional batch. Rolling with additional batch is correct because it first launches a new batch of instances in addition to the existing ones, ensuring full capacity is maintained throughout the deployment. Once the new instances are healthy, instances are updated in batches, and the original batch is terminated only after the new ones are fully serving traffic, minimizing downtime.

Answer

All at once

Answer

Rolling

Answer

Immutable

Question 7

A developer is using AWS CodeDeploy to deploy an application to an EC2 Auto Scaling group. The deployment must follow a rolling update, deploying to exactly 50% of the instances at a time. Which built-in deployment configuration should the developer use?

Accepted Answer

CodeDeployDefault.HalfAtATime. CodeDeployDefault.HalfAtATime, is correct because it instructs CodeDeploy to deploy to exactly 50% of the instances in the Auto Scaling group at a time during a rolling update. This built-in configuration ensures that half the instances are updated before the other half, matching the requirement for a 50% rolling deployment.

Answer

CodeDeployDefault.OneAtATime

Answer

CodeDeployDefault.AllAtOnce

Answer

CodeDeployDefault.LambdaAllAtOnce

Question 8

An Elastic Beanstalk deployment must avoid downtime and create a full new set of instances before swapping traffic, accepting higher temporary cost. Which policy fits?

Accepted Answer

Immutable. Immutable deployment is correct because it launches a full set of new instances in a temporary Auto Scaling group behind the same load balancer. Once the new instances pass health checks, they are promoted to the main Auto Scaling group, and the old instances are terminated. This ensures zero downtime, maintains full capacity during deployment, and allows for a clean rollback if the deployment fails, at the cost of temporarily doubling the number of instances.

Answer

All at once

Answer

Rolling

Answer

Traffic splitting disabled

Question 9

A CodeDeploy blue/green ECS deployment uses an ALB. Which two resources are required?

Accepted Answer

Two target groups for original and replacement task sets. A blue/green deployment in CodeDeploy for ECS requires two distinct target groups: one for the original (blue) task set and one for the replacement (green) task set. The ALB routes traffic to the appropriate target group based on the listener rules, allowing CodeDeploy to shift traffic from the blue to the green task set during deployment.

Answer

A single target group shared by both task sets only

Answer

An S3 static website endpoint

Answer

Listener configuration that allows traffic shifting/testing

Question 10

A developer wants separate dev and prod CloudFormation deployments from the same template. Which two practices help?

Accepted Answer

Use parameters or mappings for environment-specific values. To deploy separate dev and prod environments from the same template, you must create separate stacks (or use different stack names) for each environment (Option C). To handle environment-specific differences (such as resource sizes, AMI IDs, or database names) within that single template, you should use CloudFormation parameters or mappings (Option A). This allows the template to remain reusable and dynamic. Hardcoding production ARNs (Option B) prevents reusability, and using the root account (Option D) violates the AWS security best practice of least privilege.

Answer

Hardcode production ARNs throughout the template

Answer

Use the root account for deployments

Question 11

Drag and drop the steps to set up a CI/CD pipeline using AWS CodePipeline in the correct order.

Accepted Answer

Set up artifact storage, then set up source repository, then set up build project, then set up deployment target, then create pipeline.. To set up a CI/CD pipeline using AWS developer tools, you must first create the individual resources that the pipeline will orchestrate. This means creating the AWS CodeCommit repository (Source), the AWS CodeBuild project (Build), and the AWS CodeDeploy application/deployment group (Deploy) before finally creating the pipeline in AWS CodePipeline to link them together.

Answer

Set up source repository, then set up build project, then set up artifact storage, then set up deployment target, then create pipeline.

Answer

Create pipeline, then set up source repository, then set up build project, then set up deployment target, then set up artifact storage.

Answer

Set up deployment target, then set up source repository, then set up build project, then set up artifact storage, then create pipeline.

Question 12

A developer is deploying a serverless application using AWS SAM. The developer wants to define a Lambda function that is invoked by an Amazon API Gateway REST API. Which SAM resource type should the developer use to define the API?

Accepted Answer

AWS::Serverless::Api. AWS::Serverless::Api defines an API Gateway REST API in SAM. Option A is wrong because AWS::Serverless::SimpleTable defines a DynamoDB table, not an API. Option C is wrong because AWS::ApiGateway::RestApi is a raw CloudFormation resource, not a SAM shorthand resource type. Option D is wrong because AWS::Serverless::Function defines a Lambda function, not an API.

Answer

AWS::Serverless::SimpleTable

Answer

AWS::ApiGateway::RestApi

Answer

AWS::Serverless::Function

Question 13

A company uses AWS CodePipeline to automate deployments. The pipeline has a source stage that pulls from Amazon S3, a build stage using AWS CodeBuild, and a deploy stage using AWS CloudFormation. The deploy stage often fails because CloudFormation change sets are not being created. What is the most likely cause?

Accepted Answer

The CodeBuild project is not producing the expected output artifacts.. For AWS CloudFormation to create a change set in a CodePipeline deploy stage, it requires an input artifact containing the CloudFormation template file. If the preceding CodeBuild stage is not configured to produce the expected output artifact (or if the template file is omitted from the buildspec's artifacts section), the CloudFormation action will fail because it cannot locate the template to generate the change set.

Answer

The CloudFormation deploy action is configured to use the 'CREATE_AND_EXECUTE' change set mode, but the stack does not exist yet.

Answer

The CloudFormation service role is missing.

Answer

The source stage is not configured to detect changes in the S3 bucket.

Question 14

A developer is using AWS CodeDeploy to deploy a revision to an Amazon EC2 instance. The deployment fails 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.' Which TWO actions should the developer take to troubleshoot the issue? (Choose TWO.)

Accepted Answer

Check the CodeDeploy agent logs on the EC2 instance for errors.. The CodeDeploy agent logs on the EC2 instance contain detailed error messages about why the deployment script failed, such as script exit codes, missing dependencies, or permission issues. Checking these logs is the first step in diagnosing individual instance failures, as the agent writes events to `/var/log/aws/codedeploy-agent/codedeploy-agent.log`.

Answer

Change the deployment configuration to AllAtOnce.

Answer

Verify that the EC2 instance has an IAM role that allows CodeDeploy to access it.

Answer

Increase the health check grace period on the Auto Scaling group.

Question 15

A developer is using AWS Elastic Beanstalk to deploy a Python web application. The developer wants to run database migrations before the application starts. Which TWO methods can the developer use to achieve this? (Choose TWO.)

Accepted Answer

Use an .ebextensions configuration file with container_commands.. Options B and D are correct. Option B: .ebextensions with container_commands can run commands during deployment. Option D: A Procfile can define a command that runs migrations as part of the web process. Option A is wrong because AWS Lambda is not natively integrated with Elastic Beanstalk for pre-deployment tasks; it would require custom integration. Option C is wrong because pre-deployment hooks are not a standard Elastic Beanstalk mechanism; .ebextensions or Procfile are used instead. Option E is wrong because cron.yaml is for scheduled tasks, not for running commands during deployment.

Answer

Use an AWS Lambda function that triggers on deployment.

Answer

Add a pre-deployment hook to the application source code.

Answer

Add a cron.yaml file to schedule the migration.