DVA-C02 Development with AWS Services 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.

• ✗

  Create a separate CodeBuild project to run npm install.

  Why it's wrong here

  Creating a separate CodeBuild project does not resolve an `npm` cache integrity issue. CodeBuild environments are typically ephemeral, and while CodeBuild offers caching mechanisms, the `npm` cache itself is usually stored within the build environment's local filesystem. A new project would either start with a fresh, empty `npm` cache (which might temporarily resolve the issue but doesn't fix the root cause if it's a recurring problem) or, if CodeBuild's own caching is misconfigured, could still reuse a corrupted `npm` cache. The problem lies with the cache's content, not the project's existence.

• ✓

  Add 'npm cache verify' to the pre_build phase before 'npm install'.

  Why this is correct

  Adding 'npm cache verify' to the `pre_build` phase before 'npm install' is the correct solution because it directly addresses the cause of an 'EINTEGRITY' error. This command systematically checks the integrity of all cached packages, identifying and repairing any corrupted or incomplete entries. By ensuring the npm cache is clean and valid, subsequent 'npm install' commands will operate with correct package data, resolving the integrity mismatch without compromising security or requiring a full cache clear.

• ✗

  Add 'npm config set registry http://registry.npmjs.org/' to use HTTP.

  Why it's wrong here

  This approach is fundamentally flawed because an 'EINTEGRITY' error indicates a hash mismatch, meaning the downloaded package does not match its expected integrity checksum. Switching to an HTTP registry disables crucial HTTPS integrity checks, which are designed to prevent tampering and ensure package authenticity. While it might bypass the error by not performing the check, it severely compromises the security of your build by allowing potentially corrupted or malicious packages to be installed without detection, rather than fixing the underlying data integrity issue.

• ✗

  Use 'npm install --prefer-offline' to avoid fetching from registry.

  Why it's wrong here

  Using 'npm install --prefer-offline' instructs npm to prioritize packages from its local cache and avoid network requests if possible. However, if the 'EINTEGRITY' error stems from corruption within that local cache, this command will simply attempt to use the already corrupted data, leading to the same integrity error. It does not validate or repair the cache contents; it only changes the fetching strategy, thus failing to address the root cause of the integrity problem.

Go deeper

Related to this question