Build and Run Backstage Projects Locally CBA Practice Questions (Page 3)

Questions 11–15

1. 11foundation · easy

   What is the purpose of building a Backstage project locally?

   • ATo run the application in development mode with hot reloading.
   • BTo produce production-ready artifacts and identify build errors.
   • CTo format the code according to project style guidelines.
   • DTo execute the test suite and check for regressions.
   Reveal Solution Discussion Select an answer first
2. 12foundation · easy

   Which tool is commonly used in Backstage projects to enable hot reloading during development?

   • AWebpack Dev Server
   • BJest
   • CESLint
   • DPrettier
   Reveal Solution Discussion Select an answer first
4. 13expert · hard

   A Backstage developer is working on a large codebase and has made changes to a shared type definition. They want to ensure that all usages of the type are still valid before running the full build. The build takes a long time, so they want to check types quickly. What should the developer do?

   • ARun `yarn lint` to check for type errors.
   • BRun `yarn build` to check types and produce artifacts.
   • CRun `yarn tsc` to perform type checking across the project.
   • DRun `yarn test` to check for type errors.
   Reveal Solution Discussion Select an answer first
5. 14application · medium

   A developer is about to deploy a Backstage application to a production environment. They run `yarn build` and it fails with a TypeScript error in a plugin they recently added. The developer wants to produce a production build quickly. What should the developer do?

   • ARemove the plugin from the `app-config.yaml` and rebuild.
   • BRun `yarn build --no-type-check` to skip type checking and produce the build.
   • CFix the TypeScript error in the plugin and rerun `yarn build`.
   • DRun `yarn tsc --noEmit` to check types and then run `yarn build`.
   Reveal Solution Discussion Select an answer first
6. 15expert · hard

   A Backstage developer is preparing a production build. They have made changes to a plugin that introduce a TypeScript type error. The developer also notices that the linter reports a style violation in the same file. The developer wants to produce a build that can be deployed, but they are under time pressure. What should the developer do?

   • AFix only the type error and run `yarn build`.
   • BFix the type error and the lint violation, then run `yarn build`.
   • CRun `yarn lint --fix` to fix the lint violation and then `yarn build`.
   • DRun `yarn build` and rely on the build to fix the type error automatically.
   Reveal Solution Discussion Select an answer first