DVA-C02 Deployment Practice Test 3 — 15 Questions

Question 1

A developer is using AWS Elastic Beanstalk to deploy a web application. The application uses an Amazon RDS database instance that is included in the Elastic Beanstalk environment. The developer wants to update the application code without affecting the database. What is the recommended approach?

Accepted Answer

Decouple the database from the Elastic Beanstalk environment by creating a separate RDS instance and connecting the application to it externally.. Option C is correct because when an RDS instance is included in an Elastic Beanstalk environment, it is tied to the environment's lifecycle. If the environment is terminated or rebuilt, the database is also deleted. Decoupling the database by creating a standalone RDS instance and connecting the application to it externally ensures the database persists independently of application deployments, allowing code updates without risking data loss.

Answer

Update the application code directly on the EC2 instances without redeploying the environment.

Answer

Create a new environment configuration, update the code, and swap the CNAME of the environments.

Answer

Use Elastic Beanstalk's platform updates while keeping the database attached to the environment.

Question 2

A company uses AWS Elastic Beanstalk to deploy a web application. The development team wants to test a new feature by routing a small percentage of traffic to a separate environment before fully rolling out. Which Elastic Beanstalk deployment strategy should the developer use?

Accepted Answer

Blue/green deployment. Blue/green deployment is the correct strategy because it allows you to route a small percentage of traffic to a separate environment (the 'green' environment) by swapping the CNAME record or using Elastic Beanstalk's environment URL swap feature. This enables testing the new feature with a subset of users before fully rolling out to the 'blue' environment, minimizing risk and enabling quick rollback if issues arise.

Answer

Rolling deployment

Answer

Immutable deployment

Answer

All at once deployment

Question 3

A developer is using AWS Elastic Beanstalk to deploy a Node.js application. The application requires an environment variable that contains a secret (e.g., a database password). The developer wants to store the secret securely and make it available to the application instances. Which Elastic Beanstalk feature should be used?

Accepted Answer

Use the AWS Secrets Manager integration in Elastic Beanstalk.. AWS Elastic Beanstalk has a native integration with AWS Secrets Manager that allows you to retrieve secrets and inject them as environment variables into your application instances without exposing the secret in plaintext. This integration handles the secure retrieval and rotation of secrets automatically, making it the correct choice for securely storing and accessing a database password.

Answer

Store the secret in an environment property with the value set in plaintext.

Answer

Use an .ebextensions configuration file to set the environment variable.

Answer

Use Elastic Beanstalk platform hooks to retrieve the secret at startup.

Question 4

A developer is setting up a CI/CD pipeline using AWS CodePipeline to deploy an application to Amazon ECS. The pipeline has a source stage that pulls code from an AWS CodeCommit repository. The developer wants the pipeline to execute only when commits are pushed to the 'main' branch. How should the developer configure this?

Accepted Answer

Configure the pipeline's source stage to include the branch name in the CodeCommit action configuration.. Option B is correct because AWS CodePipeline allows you to specify a branch name directly in the source action configuration for CodeCommit. When you configure the source stage, you can set the 'BranchName' parameter to 'main', which ensures the pipeline only triggers on commits pushed to that specific branch. This is the simplest and most direct method to filter by branch without additional services or custom logic.

Answer

Create an Amazon CloudWatch Events rule that triggers the pipeline only when the branch is 'main'.

Answer

Use an AWS Lambda function in the source stage to filter the branch.

Answer

Set a branch filter pattern in the pipeline trigger settings.

Question 5

A developer is using AWS CodePipeline to deploy a web application. The pipeline has a source stage that pulls from CodeCommit and a deploy stage that uses AWS Elastic Beanstalk. The developer wants to run unit tests automatically before deploying to Elastic Beanstalk. Which action should the developer add to the pipeline?

Accepted Answer

Add a test stage that uses an AWS CodeBuild project configured to run unit tests. Option A is correct because AWS CodeBuild can be integrated as a test stage in CodePipeline to run unit tests automatically. By adding a CodeBuild project configured with a buildspec.yml file that executes unit tests, the pipeline will run tests after the source stage and before the deploy stage, ensuring only code that passes tests is deployed to Elastic Beanstalk.

Answer

Add a manual approval step before the deploy stage

Answer

Configure Elastic Beanstalk health checks to run tests

Answer

Replace Elastic Beanstalk with AWS CodeDeploy

Question 6

A developer is using AWS Elastic Beanstalk to deploy a web application. The developer wants to run database migration scripts as part of the deployment process before the new application version starts serving traffic. Which Elastic Beanstalk configuration file should the developer use to define the migration commands?

Accepted Answer

.ebextensions/.config with container_commands. Option A is correct because `container_commands` in `.ebextensions/.config` runs commands after the application and web server have been set up but before the new application version starts serving traffic. This makes it the ideal place to execute database migration scripts that must complete before the environment accepts requests, ensuring data consistency.

Answer

.ebextensions/<filename>.config with commands

Answer

Procfile

Answer

buildspec.yml

Question 7

A company runs a web application on AWS Elastic Beanstalk. The application currently runs in a single environment. The developer wants to deploy a new version with zero downtime and be able to test the new version thoroughly before it receives any production traffic. Which deployment strategy should the developer use?

Accepted Answer

Create a new environment (green) with the new version, run tests against it, and then swap the environment URLs so that production points to the green environment.. Option C is correct because it describes a blue/green deployment strategy, which creates a separate 'green' environment with the new application version, allowing thorough testing before swapping the environment URLs (CNAME records) in Elastic Beanstalk. This ensures zero downtime because the swap is instantaneous and the original 'blue' environment remains untouched until the swap occurs.

Answer

Perform a rolling deployment with a batch size of one instance at a time.

Answer

Use an immutable deployment to launch a new set of instances and then swap the Auto Scaling group.

Answer

Use a rolling deployment with additional batch to launch new instances before terminating old ones.

Question 8

A developer is deploying a new version of a web application on AWS Elastic Beanstalk. The application currently runs in a single environment with an Auto Scaling group. The developer wants to ensure zero downtime during the deployment and that the new version can be fully tested before receiving any traffic. Which Elastic Beanstalk deployment policy should the developer use?

Accepted Answer

Immutable. Immutable deployment is the correct choice because it launches a completely new Auto Scaling group with the new application version, fully tests it before shifting any traffic, and then swaps the environment's instances in a single atomic action, ensuring zero downtime. This policy meets the requirement for full testing of the new version before it receives traffic, as traffic is only routed to the new instances after they pass health checks.

Answer

All at once

Answer

Rolling

Answer

Rolling with additional batch

Question 9

A developer is using AWS CodePipeline to deploy a web application. The pipeline has stages: Source, Build, Staging Deploy, Staging Test, and Prod Deploy. The developer wants to ensure that if the Staging Test stage fails, the pipeline automatically stops and does not proceed to Prod Deploy. Which action should the developer take?

Accepted Answer

No action is needed; CodePipeline automatically stops on stage failure. Option A is correct because AWS CodePipeline's default behavior is to stop execution when a stage fails, preventing the pipeline from proceeding to subsequent stages. When the Staging Test stage fails, the pipeline transitions to a 'Failed' status and does not automatically continue to Prod Deploy. No additional configuration is required for this behavior.

Answer

Add a manual approval step before Prod Deploy

Answer

Disable the transition from Staging Test to Prod Deploy

Answer

Configure the pipeline execution mode to 'Superseded'

Question 10

A developer is using AWS CloudFormation to deploy a stack that includes an Amazon S3 bucket and an AWS Lambda function. The Lambda function needs to be granted permission to read objects from the S3 bucket. Which resource should the developer define in the CloudFormation template to provide these permissions?

Accepted Answer

AWS::IAM::Role. Option A is correct because the Lambda function requires an IAM role (AWS::IAM::Role) with a policy that grants s3:GetObject permissions on the S3 bucket. This role is assumed by the Lambda service at runtime, allowing the function to read objects from the bucket. The role must include a trust policy that allows lambda.amazonaws.com to assume it.

Answer

AWS::Lambda::Permission

Answer

AWS::S3::BucketPolicy

Answer

AWS::IAM::ManagedPolicy

Question 11

A developer has set up an AWS CodePipeline pipeline that automatically deploys a web application through a series of stages: Source, Build, Staging, and Production. The developer wants to require a manual approval before the pipeline proceeds to the Production stage. How should the developer implement this?

Accepted Answer

Add a manual approval action between the Staging and Production stages. Option B is correct because AWS CodePipeline supports manual approval actions that can be added as a stage or between stages to pause the pipeline and require explicit approval before proceeding. By placing the manual approval action between the Staging and Production stages, the pipeline will halt after the Staging stage completes and wait for an approver to manually approve the transition to the Production stage, ensuring no automatic deployment to production occurs without human oversight.

Answer

Add a manual approval action in the Staging stage

Answer

Configure the Production stage to use a CloudFormation change set with execution role

Answer

Use an SNS topic to notify developers of the deployment

Question 12

A developer uses AWS CodePipeline with a manual approval step before deployment. The developer wants to ensure that if a new commit is pushed while a pipeline execution is waiting for approval, the waiting execution is canceled and a new one starts with the latest commit. Which pipeline execution mode should be configured?

Accepted Answer

Superseded. The Superseded execution mode is designed to automatically cancel any in-progress pipeline execution when a new commit is pushed, and start a new execution with the latest source changes. This ensures that the manual approval step does not block newer commits, as the waiting execution is replaced by the one triggered by the latest commit. In contrast, other modes either queue or run executions in parallel, which would not cancel the waiting approval step.

Answer

Queued

Answer

Parallel

Answer

Single

Question 13

A developer wants to deploy a serverless application using AWS CloudFormation. The application consists of an API Gateway, Lambda functions, and DynamoDB tables. The developer wants to ensure that the stack can be updated without resource interruption when possible. Which CloudFormation feature should the developer use?

Accepted Answer

Use a Lambda alias with a DeploymentPreference update policy. Option A is correct because the `DeploymentPreference` update policy on a Lambda alias enables canary, linear, or all-at-once traffic shifting during stack updates. This allows the developer to update Lambda function versions without interrupting existing invocations, as traffic is gradually routed to the new version while the old version continues to serve requests until the transition completes.

Answer

Use a ChangeSet to review changes before applying them

Answer

Use a StackPolicy to protect critical resources

Answer

Use a Custom Resource to manage updates

Question 14

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?

Accepted Answer

Include a .ebextensions/options.config file.. Option B is correct because 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 15

A developer is using AWS CodeDeploy to deploy an application to an Auto Scaling group of EC2 instances. The developer wants to minimize the number of instances that are taken out of service at any given time during the deployment. Which predefined deployment configuration should the developer use?

Accepted Answer

OneAtATime. The OneAtATime deployment configuration shifts traffic to one new instance at a time, ensuring that only a single instance is taken out of service during the deployment. This minimizes the number of instances removed from the Auto Scaling group at any given moment, which directly meets the developer's requirement to reduce service disruption.

Answer

AllAtOnce

Answer

HalfAtATime

Answer

Custom with 50% at a time