Why is it important to commit the lock file (package-lock.json or yarn.lock) to version control in a Backstage project?

To document the purpose of each dependency in the project.

To store the credentials for private package registries.

To ensure all developers and CI environments install identical dependency versions.

To speed up the installation process by skipping network requests.

An npm install fails with an error about a corrupted cache. What is a common troubleshooting step?

Reinstall Node.js to fix the cache.

Run 'npm update' to fix the cache.

Run 'npm cache clean --force' and then re-run 'npm install'.

Delete the package-lock.json file and re-run 'npm install'.

A Backstage monorepo uses Yarn workspaces with multiple packages. A developer runs 'yarn install' at the root and notices that a dependency used by two different packages is installed only once in the root node_modules. Why does this happen?

Yarn deduplicates dependencies by default, but only for exact version matches.

Yarn workspaces hoist common dependencies to the root node_modules to avoid duplication.

Yarn install always installs dependencies only at the root, regardless of workspace configuration.

The dependency is listed in the root package.json, so it is installed only there.

A Backstage monorepo uses Yarn workspaces. A developer adds a new package to the 'packages' directory but does not add it to the 'workspaces' field in the root package.json. What will happen when they run 'yarn install'?

Yarn will automatically detect the new package and add it to the workspaces field.

The install will fail with an error about the missing workspace.

The new package's dependencies will be installed, but it will not be linked to the workspace.

The new package will be ignored, and its dependencies will not be installed.

Certified Backstage Associate (CBA)

Domain 1Objective 4

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

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 26–29

26foundation · easy
Why is it important to commit the lock file (package-lock.json or yarn.lock) to version control in a Backstage project?
Select an answer first
27foundation · easy
An npm install fails with an error about a corrupted cache. What is a common troubleshooting step?
Select an answer first
28application · medium
A Backstage monorepo uses Yarn workspaces with multiple packages. A developer runs 'yarn install' at the root and notices that a dependency used by two different packages is installed only once in the root node_modules. Why does this happen?
Select an answer first
29application · medium
A Backstage monorepo uses Yarn workspaces. A developer adds a new package to the 'packages' directory but does not add it to the 'workspaces' field in the root package.json. What will happen when they run 'yarn install'?
Select an answer first

Finished these 4 questions?

Review the revealed explanations, or continue through the curriculum.

No more pagesBack 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.