DVA-C02 Deployment 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.

• ✗

  The BeforeInstall lifecycle event is not defined in the appspec.yml

  Why it's wrong here

  If the BeforeInstall lifecycle event is not defined in the appspec.yml file, CodeDeploy would simply skip this hook during the deployment process. It would not generate a "ScriptMissing" error; instead, the deployment would proceed directly to the next defined lifecycle event, such as Install. A missing definition does not equate to a missing script file for a *defined* hook, and thus would not produce this specific error.

• ✓

  The script file specified in the appspec.yml for the BeforeInstall hook is not present on the instance

  Why this is correct

  This is the correct explanation. When CodeDeploy executes a deployment, it first downloads the application revision to the instance. If the appspec.yml specifies a script for the BeforeInstall hook, and the CodeDeploy agent cannot locate that script file at the specified path within the downloaded revision on the target instance, it will explicitly fail with a "ScriptMissing" error. This error precisely indicates that the expected script file is physically absent from the instance's file system where the agent is looking.

• ✗

  The CodeDeploy agent on the instance is not running

  Why it's wrong here

  If the CodeDeploy agent is not running on the instance, the AWS CodeDeploy service would be unable to establish communication with that instance to initiate or monitor any deployment steps. This would typically result in errors indicating connection failures, agent health issues, or an inability to reach the target instance, rather than a specific "ScriptMissing" error during a lifecycle event execution. The deployment would likely fail much earlier in the process due to a lack of agent responsiveness.

• ✗

  The instance does not have the necessary permissions to execute the script

  Why it's wrong here

  If the instance lacks the necessary permissions to execute the script specified for the BeforeInstall hook, the CodeDeploy agent would encounter a permission denied error when it attempts to run the script. This error would manifest as an "Access Denied" or similar message, indicating that the file exists but cannot be executed due to incorrect file permissions (e.g., missing executable bit) or user context. This is distinct from the script file being entirely absent from the file system.

Go deeper

Related to this question