Deploy Backstage to Production CBA Practice Questions (Page 2)

Questions 6–10

1. 6foundation · easy

   Which consideration is most important when planning a production Backstage deployment?

   • ADisabling authentication to simplify access
   • BUsing the latest version of every plugin
   • CDeploying the frontend and backend on the same server
   • DEnsuring the backend is stateless and can be scaled horizontally
   Reveal Solution Discussion Select an answer first
2. 7foundation · easy

   Which tool is commonly used to collect and visualize logs from a Backstage deployment?

   • AGrafana
   • BELK stack (Elasticsearch, Logstash, Kibana)
   • CPrometheus
   • DKubernetes
   Reveal Solution Discussion Select an answer first
4. 8expert · hard

   A company is planning to upgrade Backstage to a new minor version. They have a staging environment that mirrors production. They have tested the upgrade in staging and found no issues. However, they are concerned about the production upgrade because they have custom plugins that are not used in staging. What should they do before upgrading production?

   • AUpgrade production directly because staging tests passed.
   • BTest the custom plugins in the staging environment with the new version before upgrading production.
   • CUpgrade the custom plugins to the latest version before upgrading Backstage.
   • DRemove the custom plugins from production before upgrading.
   Reveal Solution Discussion Select an answer first
5. 9foundation · easy

   Which directory contains the output of the Backstage frontend build?

   • Anode_modules
   • Bpackages/app/dist
   • Cbuild
   • Dpackages/backend/dist
   Reveal Solution Discussion Select an answer first
6. 10application · medium

   A company has deployed Backstage to production. The operations team wants to be alerted when the backend service becomes unhealthy or when error rates exceed a threshold. They are using a monitoring stack that can scrape HTTP endpoints. What should they configure?

   • ASet up a cron job that runs `yarn backstage-cli healthcheck` every minute and sends an alert if it fails.
   • BEnable the `/healthcheck` endpoint on the backend and configure the monitoring stack to scrape it, with alerts on non-200 responses and high error rates.
   • CConfigure the monitoring stack to scrape the frontend CDN logs for errors.
   • DUse the Backstage built-in alerting feature to send emails when errors occur.
   Reveal Solution Discussion Select an answer first