Deploying — Vercel and Self-Hosting — Concept Check
Questions on Deploying — Vercel and Self-Hosting. Vercel runs Next as its authors intended and charges for it. Self-hosting is entirely viable and moves several framework features from automatic to your problem.
Questions in this quiz
7 questions on Deploying — Vercel and Self-Hosting — Concept Check. Work through them here, then start the quiz to answer them and see your score.
1.A team is using Vercel for their Next.js app. They notice an unexpected increase in costs. What is a likely cause?
- ADecreased bandwidth usage
- BIncreased function invocations and duration
- CStatic assets being served
- DReduced number of routes
2.You are self-hosting a Next.js application. What must you configure to avoid inconsistent ISR cache across instances?
- AIn-memory cache for each instance
- BA shared cache handler like Redis
- CDirect database queries for cache
- DSeparate instances for each route
3.A developer is deploying a Next.js app on Vercel. What feature is automatically handled by Vercel?
- AManual image optimization
- BCustom server setup
- CDirect database connections
- DGlobal CDN for static assets
4.While self-hosting, a team notices high CPU usage during image optimization. What is a likely solution?
- AUse a CDN loader for next/image
- BIncrease the server's RAM
- COptimize images at build time
- DDeploy more instances
5.A company wants zero-downtime deploys for their self-hosted Next.js app. What should they implement?
- ASingle-instance deployment
- BDirect database writes
- CIn-memory caching
- DHealth checks and log aggregation
6.A team is deploying a frontend and backend separately. What should they deploy first to avoid breaking a live page?
- ABackend, then frontend
- BBoth simultaneously
- CFrontend, then backend
- DFrontend only
7.A self-hosted Next.js app is experiencing slow server-rendered pages. What could be the cause?
- AHigh client-side rendering
- BExcessive static assets
- CCross-region server and database
- DLow traffic volume