What should the engineer do to identify functional issues during the deployment process?
(Choose two.)
Use Amazon Inspector to add a test action to the pipeline. Use the Amazon Inspector Runtime Behavior Analysis Inspector rules package to check that the deployed code complies with company security standards before deploying it to production.
Using AWS CodeBuild to add a test action to the pipeline to replicate common user activities and ensure that the results are as expected before progressing to production deployment.
Create an AWS CodeDeploy action in the pipeline with a deployment configuration that automatically deploys the application code to a limited number of instances. The action then pauses the deployment so that the QA team can review the application functionality. When the review is complete, CodeDeploy resumes and deploys the application to the remaining production Amazon EC2 instances.
After the deployment process is complete, run a testing activity on an Amazon EC2 instance in a different region that accesses the application to simulate user behavior. If unexpected results occur the testing activity sends a warning to an Amazon SNS topic. Subscribe to the topic to get updates.
Add an AWS CodeDeploy action in the pipeline to deploy the latest version of the development code to pre-production Add a manual approval action in the pipeline so that the QA team can test and confirm the expected functionality. After the manual approval action, add a second CodeDeploy action that deploys the approved code to the production environment.
Explanations:
Amazon Inspector is focused on security vulnerability scanning, not functional testing. The Runtime Behavior Analysis package checks for security, not for application functionality.
Using AWS CodeBuild to add a test action replicates user activities and ensures that the application is functioning correctly before deployment to production.
While CodeDeploy can limit deployment scope, this option involves manual QA review and isn’t a functional test that can identify issues automatically during deployment.
Testing on an EC2 instance in a different region after deployment is reactive, not part of the deployment pipeline, and doesn’t prevent issues from affecting production.
Using CodeDeploy with a manual approval step ensures that the QA team tests and approves functionality in pre-production before deploying to production, preventing issues.
If I’m not mistaken, the answer is:
Using AWS CodeBuild to add a test action to the pipeline to replicate common user activities and ensure that the results are as expected before progressing to production deployment.
I scheme that the answer is:
Using AWS CodeBuild to add a test action to the pipeline to replicate common user activities and ensure that the results are as expected before progressing to production deployment.