AWS Certified Developer - Associate DVA-C02 Exam Questions with Experts Answers Updated Recently

A.  

Create new Lambda function versions and aliases for the development, testing, and production accounts. After successful testing, update the production alias to point to the function version. Roll back to the most recent stable version if issues are discovered.

B.  

Deploy the Lambda function separately to the development, testing, and production accounts after testing the function in each environment.

C.  

Use Lambda layers to separate the code and libraries for each AWS account and deploy the function with different layers.

D.  

Use environment variables to differentiate development, testing, and production behavior.

A.  

Create a security group in each VPC that allows traffic only from the other fleet ' s security group. Assign each security group to the corresponding instances.

B.  

Create an AWS Site-to-Site VPN connection between the two peered VPCs. Pass the sensitive data in the API calls through the Site-to-Site VPN connection.

C.  

Create a customer managed key in AWS KMS to encrypt all EBS volumes. Create an IAM instance profile that has permission to use the customer managed key and attach the key to all instances in both fleets.

D.  

Request a valid certificate through AWS Certificate Manager (ACM) and redeploy both fleets as AWS Nitro Enclaves. Use the ACM for Nitro Enclaves Amazon Machine Image (AMI) and specify the requested certificate for all instances.

A.  

Configure AWS Secrets Manager to store the secret. Configure the env section of the buildspec.yml file to have a secrets-manager key-value entry that references the secret. Grant the CodeBuild IAM role the minimum necessary permissions to access the secret.

B.  

Store the secret in an encrypted Amazon S3 bucket. Download the secret during the build process. Use NoEcho to mask the value of the secret. Grant the CodeBuild IAM role the minimum necessary permissions to access the S3 bucket.

C.  

Configure AWS Systems Manager Parameter Store to store the secret. Configure the env section of the buildspec.yml file to have a parameter-store key-value entry that references the parameter. Grant the CodeBuild IAM role the minimum necessary permissions to access the parameter.

D.  

Store the secret in AWS Systems Manager Parameter Store. Use a pre-build step to retrieve the parameter by using AWS CLI commands. Mask the parameter in the buildspec.yml file. Grant the CodeBuild IAM role the minimum necessary permissions to access the parameter.

A.  

Write a Git pre-commit hook that runs the test before every commit. Ensure that each developer who is working on the project has the pre-commit hook instated locally. Review the test report and resolve any issues before pushing changes to AWS CodeCommit.

B.  

Add a new stage to the pipeline. Use AWS CodeBuild as the provider. Add the new stage after the stage that deploys code revisions to the test environment. Write a buildspec that fails the CodeBuild stage if any test does not pass. Use the test reports feature of Codebuild to integrate the report with the CodoBuild console. View the test results in CodeBuild Resolve any issues.

C.  

Add a new stage to the pipeline. Use AWS CodeBuild at the provider. Add the new stage before the stage that deploys code revisions to the test environment. Write a buildspec that fails the CodeBuild stage it any test does not pass. Use the test reports feature of CodeBuild to integrate the report with the CodeBuild console. View the test results in codeBuild Resolve any issues.

D.  

Add a new stage to the pipeline. Use Jenkins as the provider. Configure CodePipeline to use Jenkins to run the unit tests. Write a Jenkinsfile that fails the stage if any test does not pass. Use the test report plugin for Jenkins to integrate the repot with the Jenkins dashboard. View the test results in Jenkins. Resolve any issues.