DOP-C02 SDLC Automation 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 npm install command is running before the source is downloaded.

  Why it's wrong here

  CodeBuild automatically downloads the repository source code before any build commands are executed. The build phases run in a fixed order: source checkout happens before install, so the workspace always contains the downloaded source when `npm install` starts. If the source were somehow absent, the install phase could not even find `package.json`, producing a different error about a missing manifest, not a missing module.

• ✗

  The lodash package is not compatible with the Node.js version.

  Why it's wrong here

  If lodash were incompatible with the configured Node.js version, `npm install` would typically fail with an `engine` warning or a compile-time error, and the build would stop before producing an artifact. A "Cannot find module 'lodash'" runtime error indicates the package was never installed into `node_modules`, which is a dependency declaration or installation problem, not a version compatibility problem.

• ✓

  The package.json file is missing or does not include lodash.

  Why this is correct

  `npm install` reads the `dependencies` and `devDependencies` fields in `package.json` and installs exactly the packages listed there. If lodash is not specified in that file, it will not be installed, and any subsequent `require('lodash')` or `import ... from 'lodash'` will throw `MODULE_NOT_FOUND`. A missing `package.json` would cause `npm install` to fail outright, but either way, the root cause is that lodash was not properly declared as a dependency.

• ✗

  The build environment does not have internet access to download packages.

  Why it's wrong here

  Packages are downloaded from the npm registry during the install phase. If the build environment had no internet access, `npm install` would fail with a network error such as `ENOTFOUND`, `ETIMEDOUT`, or an `ECONNREFUSED` — not a module-not-found error at build time. The error message about lodash being missing means the install step either did not include lodash or was skipped for that package, not that network connectivity was the issue.

Go deeper

Related to this question