A developer is working on a Backstage project and notices that the package-lock.json file is missing from the repository. What is the most likely consequence of this?

Different developers may get different versions of dependencies.

npm install will be faster because it skips lock file processing.

The project will not be able to use workspaces.

npm install will fail because the lock file is required.

A developer is troubleshooting a failed 'npm install' in a Backstage project. The error message indicates that a package tarball cannot be fetched because of a checksum mismatch. The developer has already cleared the npm cache and retried, but the error persists. What is the most likely cause and solution?

The npm registry is down, causing corrupted downloads.

The package-lock.json has an incorrect integrity hash for the package.

The package version does not exist on the registry.

The node_modules folder is corrupted and needs to be deleted.

A Backstage monorepo uses npm workspaces. A developer notices that after running 'npm install', the package-lock.json file has been modified, but they did not intentionally change any dependencies. What is the most likely cause?

The npm registry has published new versions of the dependencies.

The package.json files in the workspaces have been updated with new dependency ranges.

The lock file was not committed to the repository, so npm regenerated it.

The node_modules folder was corrupted and npm had to re-resolve dependencies.

Certified Backstage Associate (CBA)

Domain 1Objective 4

Download and Install Dependencies for a Backstage Project with NPM/Yarn CBA Practice Questions (Page 2)

Part of the Backstage Development Workflow domain, which accounts for 24% of the CBA exam. Linux Foundation does not publish an official question count, but from its 90-minute exam (~35–60 total, ~8–14 in this domain), expect 2–3 from this objective — we provide 29 practice questions to prepare you well beyond it. (estimate)

29questions here

6free pages

8concepts

24%of the exam

Questions 6–10

6application · medium
A developer is working on a Backstage project and notices that the package-lock.json file is missing from the repository. What is the most likely consequence of this?
Select an answer first
7expert · hard
A developer is troubleshooting a failed 'npm install' in a Backstage project. The error message indicates that a package tarball cannot be fetched because of a checksum mismatch. The developer has already cleared the npm cache and retried, but the error persists. What is the most likely cause and solution?
Select an answer first
8foundation · easy
Which command installs dependencies for a Backstage project when the repository uses Yarn as its package manager?
Select an answer first
9expert · hard
A Backstage monorepo uses npm workspaces. A developer notices that after running 'npm install', the package-lock.json file has been modified, but they did not intentionally change any dependencies. What is the most likely cause?
Select an answer first
10foundation · easy
Which file is used by npm to ensure that the same dependency versions are installed across different environments?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to CBA

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Linux Foundation. “CBA” is a trademark of its owner, used for identification only.

Download and Install Dependencies for a Backstage Project with NPM/Yarn CBA Practice Questions (Page 2)

Questions 6–10

A developer is working on a Backstage project and notices that the package-lock.json file is missing from the repository. What is the most likely consequence of this?

Which command installs dependencies for a Backstage project when the repository uses Yarn as its package manager?

A Backstage monorepo uses npm workspaces. A developer notices that after running 'npm install', the package-lock.json file has been modified, but they did not intentionally change any dependencies. What is the most likely cause?

Which file is used by npm to ensure that the same dependency versions are installed across different environments?

Keep studying — Backstage Development Workflow