DVA-C02 Deployment Practice Test 15 — 15 Questions

Question 1

A developer is using AWS CodeBuild to build a Java application. The buildspec.yml file includes commands to run unit tests and package the application. Recently, the build started failing with the error 'No space left on device.' The developer notices that the build environment is using the general1.large compute type with 8 GB of disk space. The developer needs to resolve the disk space issue without modifying the application code. The build environment is managed by CodeBuild and the developer cannot change the instance type. What should the developer do?

Accepted Answer

Add a command in the buildspec.yml to clean the cache directory before the build phase.. Option D is correct because cleaning up the cache before building frees up disk space. Option A is wrong because CodeBuild does not allow mounting EBS volumes. Option B is wrong because EFS cache is not supported. Option C is wrong because the instance type cannot be changed. The error is due to disk space exhaustion, and clearing the cache resolves it.

Answer

Use an Amazon EFS file system as a cache to store dependencies.

Answer

Change the compute type to general1.medium with 8 GB disk space.

Answer

Mount an additional Amazon EBS volume to the build container.

Question 2

A developer is using AWS CloudFormation to deploy a stack that includes an Amazon S3 bucket with a bucket policy that grants public read access. The stack creation fails with the error 'Access Denied for bucket: bucket-policy does not allow access.' The developer has full administrative permissions in AWS. The developer verifies that the bucket policy is correctly formatted. What is the most likely cause of the failure?

Accepted Answer

The S3 Block Public Access settings are enabled at the account level, preventing the bucket policy from granting public access.. Option A is correct because S3 bucket policies that grant public access require the S3 Block Public Access settings to be disabled at the account or bucket level. Option B is wrong because the bucket name is not the issue. Option C is wrong because KMS is not involved. Option D is wrong because the policy is correct.

Answer

The developer does not have permissions to create S3 buckets.

Answer

The S3 bucket name is already in use by another account.

Answer

The S3 bucket is encrypted with AWS KMS, and the bucket policy does not include kms:Decrypt permissions.

Question 3

A company uses AWS CodeDeploy to deploy a web application to an Auto Scaling group. 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.' The deployment group has a minimum of 2 instances and a maximum of 4. The deployment configuration is CodeDeployDefault.OneAtATime. What is the most likely cause of the failure?

Accepted Answer

The Auto Scaling group has only 2 instances, and one instance fails during deployment, leaving less than the required healthy instances.. Option A is correct because the deployment configuration specifies one instance at a time, but the Auto Scaling group may have only 2 instances, which is the minimum. If one instance fails, the healthy count drops below the required threshold, causing the deployment to fail. Option B is wrong because the IAM role typically does not cause such errors. Option C is wrong because the deployment group size is not the issue. Option D is wrong because the revision is uploaded, not the cause.

Answer

The deployment group's maximum instances is set to 4, which exceeds the number of instances in the Auto Scaling group.

Answer

The IAM role attached to the instances does not have sufficient permissions to download the revision from Amazon S3.

Answer

The revision is not properly zipped or the AppSpec file is missing.

Question 4

A development team uses AWS Elastic Beanstalk to deploy a containerized application. They notice that after a successful deployment, the environment's health turns from Green to Red. The application logs show no errors. What is the most likely cause?

Accepted Answer

The ELB health check endpoint returns a 503 status code after the new version is deployed.. Option B is correct because Elastic Beanstalk uses an ELB health check to determine environment health. If the health check path returns a non-200 status, the environment turns red. Option A is wrong because it would cause deployment failure, not post-deployment health issues. Option C is wrong because it would cause scaling issues, not immediate health change. Option D is wrong because it would affect deployment, not health.

Answer

The deployment failed due to a missing environment variable.

Answer

The application's Docker image is not compatible with the platform version.

Answer

The Auto Scaling group's minimum instance count is too low.

Question 5

A company uses AWS CodeBuild to compile and package code, and AWS CodePipeline to orchestrate deployments to Amazon ECS. The pipeline includes a manual approval step. During a recent deployment, the build succeeded but the pipeline failed at the deploy stage with the error 'CannotPullContainerError: manifest for image:tag not found'. The ECS task definition references the image:tag. What is the most likely cause?

Accepted Answer

The image tag used is 'latest', and a subsequent build pushed a new 'latest' image, overwriting the original before the manual approval was granted.. Option D is correct because the manual approval step may cause a delay, and if the image tag is 'latest', it may be overwritten by a subsequent build, causing the image to be unavailable. Option A is wrong because the build succeeded. Option B is wrong because the error is about manifest, not networking. Option C is wrong because the task definition is correct at the time of deployment.

Answer

The CodeBuild project does not have permissions to push to Amazon ECR.

Answer

The ECS cluster does not have internet access to pull the image from ECR.

Answer

The task definition references an incorrect image name.

Question 6

A company is deploying a critical application using AWS CodeDeploy. To minimize downtime, they want to perform a blue/green deployment. Which TWO strategies should they implement?

Accepted Answer

Create an Elastic Load Balancer to route traffic between the blue and green environments.. Option B (use an Elastic Load Balancer) is correct because blue/green deployments require traffic switching between environments. Option D (register instances with the ELB) is correct because the new instance group must be registered to receive traffic. Option A is wrong because a 'swap' is not a standard approach. Option C is wrong because DNS changes are not typically used with CodeDeploy. Option E is wrong because CodeDeploy does not support A/B testing natively.

Answer

Use an Amazon Route 53 weighted routing policy to gradually shift traffic.

Answer

Configure an AWS Lambda function to perform A/B testing during deployment.

Answer

Use an Amazon CloudFront distribution with multiple origins.

Question 7

A company uses AWS CloudFormation to manage infrastructure. They need to update a stack that includes an Amazon RDS DB instance. To minimize downtime, they want to perform a rolling update. Which THREE properties must be set in the CloudFormation template?

Accepted Answer

CreationPolicy attribute with ResourceSignal. Option A (UpdatePolicy with AutoScalingReplacingUpdate) is correct for rolling updates on Auto Scaling groups. Option B (CreationPolicy with ResourceSignal) is correct to wait for signals. Option D (DeletionPolicy) is incorrect because it controls deletion behavior. Option C (UpdatePolicy with AutoScalingRollingUpdate) is correct for rolling update configuration. Option E (UpdatePolicy with UseOnlineResizing) is not a valid property. So correct are A, B, C.

Answer

DeletionPolicy attribute set to Snapshot

Answer

UpdatePolicy attribute with UseOnlineResizing

Question 8

A developer is using AWS CodePipeline to automate deployments. The pipeline has a Source stage using Amazon S3 and a Deploy stage using AWS Elastic Beanstalk. The developer notices that the pipeline fails at the Deploy stage with the error 'The deployment failed because the version of the application to be deployed could not be found.' Which TWO actions should the developer take to resolve this issue?

Accepted Answer

Ensure that the S3 bucket and the Elastic Beanstalk environment are in the same AWS region.. Option B (Ensure the S3 bucket is in the same region) is correct because cross-region access requires explicit configuration. Option D (Check that the source artifact is a zip file) is correct because Elastic Beanstalk expects a zip. Option A is wrong because the bucket name is not an issue. Option C is wrong because it's a separate service. Option E is wrong because the S3 key is typically correct.

Answer

Make sure the source artifact is a valid zip file containing the application code and environment configuration.

Answer

Confirm that the S3 object key does not contain special characters.

Answer

Verify that the S3 bucket name is exactly as specified in the pipeline.

Question 9

A company is using AWS CodeDeploy to deploy an application to an Auto Scaling group. The deployment group has a deployment configuration of CodeDeployDefault.AllAtOnce. During a deployment, some instances fail the deployment. Which THREE actions should the developer take to improve the deployment health?

Accepted Answer

Change the deployment configuration to CodeDeployDefault.OneAtATime.. Option A (use CodeDeployDefault.OneAtATime) is correct because it reduces risk by deploying to one instance at a time. Option B (add a health check) is correct to catch issues early. Option D (use lifecycle hooks) is correct to run tests before instances are marked healthy. Option C is wrong because it does not help with deployment failures. Option E is wrong because it does not affect deployment health.

Answer

Increase the minimum number of healthy instances in the Auto Scaling group.

Answer

Use a larger instance type to handle the deployment load.

Question 10

A startup is deploying a Node.js application using AWS Elastic Beanstalk. They have configured the environment to use a load-balanced, auto-scaled environment with a minimum of 2 instances and a maximum of 4. The application connects to an Amazon RDS MySQL database. After a successful deployment, users report that the application is intermittently returning errors. The developer checks the Elastic Beanstalk logs and finds that the application is timing out when connecting to the database. The developer also notices that the database connection string is hardcoded in the application code. What is the most likely cause of the intermittent errors?

Accepted Answer

The RDS instance has reached its maximum number of concurrent connections because the application instances are not using connection pooling.. Option C is correct because when using a hardcoded connection string, each instance tries to connect using the same credentials, but RDS has a limit on the number of concurrent connections. As instances scale up, they may exceed the limit, causing intermittent timeouts. Option A is wrong because the security group is likely correct. Option B is wrong because RDS Multi-AZ is for failover, not connection limits. Option D is wrong because the errors are database-related, not application logic.

Answer

The security group for the RDS instance does not allow inbound traffic from the Elastic Beanstalk environment's security group.

Answer

The application code has a bug that causes the database connection to be closed prematurely.

Answer

The RDS instance is not configured for Multi-AZ deployment, causing failover issues.

Question 11

A company is using AWS CodePipeline to automate the deployment of a microservices application to Amazon ECS. The pipeline has the following stages: Source (GitHub), Build (CodeBuild), Deploy (ECS). The Deploy stage uses an ECS task definition and updates the service. Recently, the pipeline failed at the Deploy stage with the error: 'The task definition family is inactive.' The developer checks the ECS console and sees that the task definition family exists but is inactive. The developer also notices that the pipeline uses a parameter 'TASK_DEFINITION_FAMILY' with the value 'my-app'. What is the most likely cause?

Accepted Answer

The pipeline is referencing the task definition family name without a specific revision number, and the latest revision is inactive.. Option B is correct because CodePipeline expects a specific revision number, not just the family. When the family is inactive, it may be because the latest revision is inactive. The pipeline should reference the active revision. Option A is wrong because the family exists. Option C is wrong because the task role is not related. Option D is wrong because the environment variables are likely correct.

Answer

The task definition family 'my-app' does not exist in the ECS cluster.

Answer

The environment variables in the task definition are not correctly set.

Answer

The IAM role for ECS does not have permission to register new task definitions.

Question 12

A large enterprise is deploying a critical application across multiple AWS regions using AWS CodePipeline and AWS CodeDeploy. The application runs on EC2 instances in an Auto Scaling group. The deployment uses a blue/green strategy. During a cross-region deployment, the pipeline fails in the secondary region with the error 'The deployment group does not exist.' The developer confirms that the deployment group exists in the primary region and has been replicated via AWS CloudFormation StackSets. The developer also checks that the StackSet is successfully deployed in the secondary region. What is the most likely cause?

Accepted Answer

The CodePipeline in the secondary region references the deployment group ARN from the primary region instead of the secondary region.. Option D is correct because CodePipeline is region-specific and the pipeline in the secondary region must be configured to use the deployment group in that same region. The StackSet may have created the resources, but the pipeline definition still points to the primary region. Option A is wrong because the deployment group does exist. Option B is wrong because the pipeline exists. Option C is wrong because permissions are global.

Answer

The deployment group name is case-sensitive and differs between regions.

Answer

The CodePipeline in the secondary region is not configured with the correct source stage.

Answer

The IAM role for CodeDeploy in the secondary region does not have cross-region permissions.

Question 13

A developer is deploying a serverless application using the AWS Serverless Application Model (SAM). The application consists of an AWS Lambda function and an Amazon API Gateway REST API. The developer runs 'sam deploy' but the deployment fails with the error: 'Error: Security Constraints Not Satisfied'. The developer checks the IAM policies and confirms that the Lambda function has the necessary permissions. What is the most likely cause?

Accepted Answer

The API Gateway endpoint is configured with 'OPEN' access without any authorization.. Option A is correct because SAM enforces security constraints, and if the API is configured with open access (e.g., no authorization), SAM deployment will fail. Option B is wrong because SAM does not require a VPC. Option C is wrong because SAM manages S3 buckets. Option D is wrong because the error is about security constraints.

Answer

The Lambda function is not configured to run inside a VPC.

Answer

The SAM template does not specify an S3 bucket for the deployment artifacts.

Answer

The Lambda function's memory size is set too high.

Question 14

A company uses AWS CodeCommit for source control and AWS CodeBuild for building a Java application. They have a CodePipeline that deploys the built artifacts to an Auto Scaling group using CodeDeploy. Recently, the build stage started failing with the error: 'BUILD FAILED: Could not resolve dependencies for project'. The developer checks the buildspec.yml and sees that it uses Maven to download dependencies from a private repository. The developer also notices that the build environment is a managed Docker image. What is the most likely cause?

Accepted Answer

The build environment does not have network access to the private Maven repository because it is not configured with a VPC.. Option B is correct because a managed Docker image may not have network access to a private repository if it's not configured with a VPC or NAT gateway. Option A is wrong because CodeBuild supports private repositories with proper network configuration. Option C is wrong because the buildspec is correct. Option D is wrong because the error is about dependency resolution, not compilation.

Answer

The CodeBuild project does not have the necessary IAM permissions to access the private Maven repository.

Answer

The buildspec.yml has a syntax error in the 'phases' section.

Answer

The Java compiler version is incompatible with the project.

Question 15

A company is deploying a microservices application on Amazon ECS using the Fargate launch type. The application includes a service that must process messages from an Amazon SQS queue. The developer wants to ensure that the service scales based on the number of messages in the queue. Which scaling solution should the developer implement?

Accepted Answer

Use Amazon ECS Service Auto Scaling with a target tracking scaling policy based on the SQS queue backlog per task.. Option C is correct because Amazon ECS Service Auto Scaling with a target tracking scaling policy based on the SQS queue backlog can automatically adjust the number of tasks. Option A is wrong because Application Auto Scaling with a scheduled scaling policy is not dynamic. Option B is wrong because DynamoDB auto scaling is for database throughput, not ECS tasks. Option D is wrong because Lambda reserved concurrency limits the number of concurrent executions but does not scale ECS tasks.

Answer

Configure DynamoDB auto scaling to adjust read capacity based on queue depth.

Answer

Configure AWS Lambda with reserved concurrency and trigger it from the SQS queue.

Answer

Use Application Auto Scaling with a scheduled scaling policy to increase the number of tasks during peak hours.