Deploying a Frontend and a Backend — Concept Check
Questions on Deploying a Frontend and a Backend. Two deployables means two pipelines, and the ordering between them matters: a backend change can break a frontend that is still serving the previous bundle.
Questions in this quiz
8 questions on Deploying a Frontend and a Backend — Concept Check. Work through them here, then start the quiz to answer them and see your score.
1.Your frontend is deployed on Vercel and the backend on Fly. After deploying a new backend version, users report issues with the frontend. What is the likely cause?
- AThe backend deployment failed, causing frontend issues.
- BThe frontend was not updated to match the new backend API.
- CVercel does not support the new backend changes.
- DThe frontend build command was incorrect.
2.During a deployment, the backend's release_command fails. What happens next?
- AThe deployment is aborted, and the old version continues serving.
- BThe deployment proceeds but with limited functionality.
- CThe database schema is reverted to the previous state.
- DThe frontend is automatically rolled back.
3.A developer adds a new column to a database and deploys the backend first. What should they ensure before deploying the frontend?
- AThe backend is rolled back to match the frontend.
- BThe new column is populated with default values.
- CThe frontend code reads from both the old and new columns.
- DThe frontend can still function without the new column.
4.Why is it recommended to deploy the backend before the frontend in a two-pipeline deployment?
- ATo minimize downtime during deployment.
- BTo allow rollback of the frontend if needed.
- CTo test the frontend with the new backend first.
- DTo ensure the new API can serve the old frontend.
5.After deploying a frontend update, users see a 404 error when accessing a lazy-loaded route. What should you do?
- AClear the browser cache and cookies.
- BDeploy the backend again to fix the issue.
- COffer a page reload to the user.
- DRollback the frontend deployment immediately.
6.A developer mistakenly believes that deploying the frontend first is safer. What is the flaw in this reasoning?
- AThe frontend rollback is more complex than the backend.
- BThe new frontend may call API endpoints that don't exist yet.
- CThe frontend deployment takes longer than the backend.
- DThe backend cannot handle requests from the old frontend.
7.What is a critical step before deploying a backend with database migrations?
- ADeploying on a Friday evening for quick fixes.
- BRemoving old database fields immediately.
- CTesting the migration against a copy of production data.
- DEnsuring the frontend is already updated.
8.Why must database changes be additive during deployments?
- ATo speed up the deployment process.
- BTo allow rollbacks without breaking existing functionality.
- CTo simplify the backend deployment script.
- DTo reduce the need for frontend updates.