DOP-C02 Configuration Management and IaC Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  Use a custom Chef recipe in the layer's configuration to run the installation.

  Why this is correct

  A custom Chef recipe assigned to a layer's Setup lifecycle event is the correct way to run arbitrary installation steps. AWS OpsWorks automatically executes the Setup event on every instance as it finishes bootstrapping, and any recipe you attach to that event runs at that point. This allows you to invoke an `execute` resource or package installer for a third-party agent, beyond the built-in packages OpsWorks configures.

• ✗

  Define the agent installation in the layer's built-in configuration.

  Why it's wrong here

  The built-in configuration of an OpsWorks layer only controls which AWS-managed packages and system services are installed for that layer's type (e.g., Apache for a PHP web layer). It does not provide a hook to run arbitrary commands or install third-party agents, because those built-in parameters map to recognized Chef attributes used by OpsWorks' own setup recipes. Custom actions like installing a monitoring agent require a custom recipe assigned to a lifecycle event.

• ✗

  Use custom JSON to pass the installation commands.

  Why it's wrong here

  Custom JSON in OpsWorks supplies Chef node attributes to the stack's cookbooks; it is data consumed by recipes, not an execution engine. Passing commands as JSON would only make those strings available as attributes, and unless a recipe explicitly reads them and runs them via `execute`, they have no effect. This option conflates configuration data with imperative action, so it cannot trigger an installation by itself.

• ✗

  Create a cookbook repository and upload the agent installation script.

  Why it's wrong here

  Creating a cookbook repository and uploading an installation script is only the first step; cookbooks in that repository must be associated with the stack and their recipes must be explicitly assigned to lifecycle events on a layer. Without that assignment, the script remains inert source code—the Chef client never runs it. A repository alone never executes anything; you need a recipe with an `execute` resource and a lifecycle hook to invoke that recipe on instance setup.

Go deeper

Related to this question