AWS DevOps Engineer Professional Practice Test

Disable ads (and more) with a membership for a one time $2.99 payment

Prepare for the AWS DevOps Engineer Professional Test with comprehensive flashcards and multiple choice questions. Each question is accompanied by helpful hints and explanations to guide your study. Get exam-ready with confidence!

Each practice test/flash card set has 50 randomly selected questions from a bank of over 500. You'll get a new set of questions each time!

Practice this question and more.


What steps are needed to deploy application revisions in AWS CodeDeploy for EC2/on-premise instances?

  1. Create an application; specify the deployment group; specify the deployment configuration; upload the revision

  2. Specify application; define environment; configure permissions; upload archive

  3. Create deployment plan; configure scaling; set permissions; deploy application

  4. Define service; create target group; specify health check; upload application

The correct answer is: Create an application; specify the deployment group; specify the deployment configuration; upload the revision

To successfully deploy application revisions in AWS CodeDeploy for EC2/on-premise instances, the first step is to create an application within CodeDeploy. This application serves as a logical grouping for the deployments. Next, a deployment group is specified, which organizes the instances targeted for the deployment and can include settings like tags or Auto Scaling groups. Following that, the deployment configuration is defined, which outlines how the deployment should be carried out, such as whether it should be a "blue/green" or "in-place" deployment. Finally, you upload the revision of the application code, typically in the form of a ZIP or TAR file that contains the application files and the AppSpec file, which defines how the application should be deployed. The other options do not accurately reflect the procedure for deploying applications using AWS CodeDeploy. They either include components irrelevant to the CodeDeploy service or omit crucial steps necessary for the deployment process. For example, defining a service and creating a target group are more aligned with Amazon ECS or Elastic Load Balancing rather than CodeDeploy.