DOP-C02 Domain 2: Configuration Management and Infrastructure as Code

A DevOps engineer launched Elastic Beanstalk with the EB CLI and added an .ebextensions file that sets the instance type to t3.medium. The environment picked up new environment variables but still runs t3.small instances. What is the most likely root cause?

Multiple choice — select one answer

Answer choices

  1. a. AWS OpsWorks or SSM State Manager
  2. b. cfn-lint and CloudFormation change sets
  3. c. Systems Manager Compliance and AWS Config
  4. d. Values passed through the Elastic Beanstalk CLI/API (recommended values) take precedence over .ebextensions for settings such as instance type.

Architectural breakdown & explanation

Precedence is direct environment/API settings, saved configuration, .ebextensions, then defaults. CLI launches can apply recommended values that win over extensions.

Correct answer(s): d. Values passed through the Elastic Beanstalk CLI/API (recommended values) take precedence over .ebextensions for settings such as instance type.

Exam domain: Domain 2: Configuration Management and Infrastructure as Code (17% weight on the official guide).

Official documentation & study links

Practice this certification

This page is one question from the AWS Certified DevOps Engineer – Professional bank. Run a full timed practice exam with domain-weighted random questions in your browser.