Certified Backstage Associate case studies
Certified Backstage Associate · Put your knowledge to work in context.
The Certified Backstage Associate (CBA) is a Linux Foundation certification that validates practical skill with Backstage, the open source framework for building internal developer portals and standardized developer platforms. The source page positions it around developer and engineering onboarding, cross-team collaboration, and product innovation, and frames the credential as proof that a holder can work with Backstage to build standardized developer platforms. It is aimed at a beginner experience level, so it suits developers, platform engineers, and DevOps practitioners who are starting to build or operate a Backstage-based portal rather than specialists with years of framework experience. The exam is delivered online with proctoring in multiple-choice format and runs 90 minutes. The Certified Backstage Associate case studies are 5 cases and about 2,964 words.
1The 38-Minute Pull Request
Acme's Backstage monorepo has grown to 62 workspace packages: 14 frontend plugins, 9 backend plugins, 4 shared libraries, and the app/backend packages. A pull request currently runs yarn tsc , yarn lint , yarn test , and yarn build across the whole workspace.
627 words, about 3 min2TechDocs OOM and the Intermittent 401s
Contoso runs Backstage 1.2x on EKS with three backend replicas behind an ALB. The backend image includes MkDocs and the TechDocs local builder; 90 of 1,200 catalog entities have docs.
624 words, about 3 min3The Catalog That Ate GitHub's Rate Limit
Fabrikam's catalog is fed by a script that writes 450 type: url locations into a single locations.yaml , one per repository. Every five minutes the catalog refreshes all of them.
551 words, about 3 min4The Tab That Should Not Appear for Resources
Northwind's Backstage app has 14 plugins and a customized entity page in packages/app/src/components/catalog/EntityPage.tsx . The platform team wants a new Deployments tab that appears only for kind: Component with spec.type: service and the annotation backstage.io/kubernetes-id .
577 words, about 3 min5The Ownership Graph That Never Resolves
Litware has 800 Components and 240 Systems. spec.owner values are GitHub team slugs such as payments-core , but the catalog contains no Group entities for most of them.
585 words, about 3 min