Deploy Backstage to Production CBA Practice Questions (Page 3)

Questions 11–15

1. 11foundation · easy

   What should be included in a backup strategy for a production Backstage deployment?

   • AThe container images
   • BOnly the backend logs
   • COnly the frontend static assets
   • DThe database and configuration files
   Reveal Solution Discussion Select an answer first
2. 12application · medium

   A company is implementing a disaster recovery plan for Backstage. They want to ensure that if the primary region fails, they can restore service in a secondary region. What should they include in their plan?

   • AStore the database backups only in the primary region.
   • BRely on the CDN to serve the frontend and do not plan for backend recovery.
   • CKeep a standby backend running in the secondary region at all times.
   • DRegularly back up the database and configuration, and document the steps to redeploy the backend and frontend in the secondary region.
   Reveal Solution Discussion Select an answer first
4. 13application · easy

   A team is building Backstage for production deployment. They want to ensure the build output is optimized and does not include development-only code. Which command should they use?

   • A`yarn tsc`
   • B`yarn build`
   • C`yarn start`
   • D`yarn build:dev`
   Reveal Solution Discussion Select an answer first
5. 14foundation · easy

   Which of the following is a recommended way to manage secrets in a production Backstage deployment?

   • AUsing a secret management service
   • BStoring them in a public configuration file
   • CHardcoding them in the source code
   • DEmbedding them in the frontend bundle
   Reveal Solution Discussion Select an answer first
6. 15application · medium

   A company is preparing to deploy Backstage to production. The security team requires that all secrets, such as database credentials and authentication provider client secrets, be stored in a managed secret store and injected into the application at runtime. The operations team wants to avoid storing any secrets in the application configuration files. Which approach should the team use?

   • AUse the Backstage CLI to encrypt secrets and store them in the app-config.yaml file.
   • BHardcode the secrets in the backend Docker image and rely on image registry access controls.
   • CPlace the secrets in the app-config.production.yaml file and restrict file permissions to the service account.
   • DSet the secrets as environment variables in the container orchestration platform and reference them in the Backstage configuration using the standard ${VAR} syntax.
   Reveal Solution Discussion Select an answer first