Submitting the final quiz unlocks your grade, Leaderboard points, and Certificate.
◆ Only one answer is 100%. Others may count 75% or 50% — your final grade reflects this. At the end you'll see the correct answers for all questions.
⚠️ Submit once and be patient — your grade can take up to 30 minutes.
After you submit, our pipeline processes your result automatically. This can take up to 30 minutes — that's normal. If you submit a second time thinking something went wrong, the pipeline will detect the duplicate and only your first submission counts . Your grade, Leaderboard points, and Certificate will not be processed for the repeat. Submit once, then wait.
After up to 30 minutes, find your grade at members.builderscamp.com and your Certificate at members.builderscamp.com/certificates .
Good luck. 🤞
1. What is the primary purpose of the Problem Statement Framework in Lovable?
A) To define technical requirements and architecture before any coding starts. B) To clearly articulate the problem being solved before building, keeping the product focused on real user needs. C) To create a visual prototype of the product before development begins. D) To write automated tests that validate the application's behavior before shipping.
2. When preparing design assets for Lovable, what is the recommended approach?
A) Find design inspiration sources and reference an established design system (like shadcn/ui) to guide Lovable's output. B) Build all designs from scratch using custom CSS — it gives the most control over the output. C) Export designs directly from Figma and upload them as-is for Lovable to implement. D) Skip design prep entirely and rely on Lovable to generate all visuals from scratch.
3. Which starting strategy best suits a well-defined project with specific design requirements?
A) YOLO — start building immediately without any upfront context or references. B) Template — pick a pre-built template that's closest to your vision and customize from there. C) Starting Prompt only — describe everything in one long initial message. D) Starting Prompt with design references and a clear problem context loaded upfront.
4. What is the role of masterplan.md in a Lovable project?
A) Stores environment variables and API configuration for the project. B) Tracks completed features and serves as the project's changelog. C) Serves as the high-level PRD — defining vision, core features, and project scope for Lovable's context. D) Lists the ordered sequence of tasks Lovable should implement next.
5. How does tasks.md function in the "Build like a Product Trio" workflow?
A) Documents known bugs and technical debt to be addressed in future sprints. B) Acts as a prioritized backlog of features and tasks that drives what Lovable builds next. C) Stores raw user research notes and interview transcripts for the team to reference. D) Defines the app's routing structure and page hierarchy for Lovable to follow.
6. What is the main benefit of configuring the Knowledge Base in Lovable?
A) It enables Lovable to auto-deploy your app to production on each save. B) It securely stores user authentication tokens across sessions. C) It speeds up Lovable's code generation by caching your most frequent prompts. D) It gives Lovable persistent project context, so you don't have to re-explain your stack, rules, or decisions in every prompt.
7. In Lovable Cloud, what do user roles and permissions primarily control?
A) What actions different users can perform within the application — read, write, admin, and so on. B) The visual theme and layout each user sees on their personalized dashboard. C) How much cloud storage is allocated to each user account. D) Which third-party integrations are visible to each team member in the builder.
8. When integrating Paddle payments in Lovable, what is the fee structure?
A) A flat percentage of monthly revenue, billed as a single amount at the end of each cycle. B) Free for the first 100 transactions, then 2% per transaction thereafter. C) 3% + $0.30 per transaction — matching Stripe's standard rate. D) 5% + 50¢ per transaction.
9. What is the key difference between Build mode and Plan mode in Lovable?
A) Build mode handles frontend changes; Plan mode generates backend API routes. B) They are interchangeable — the names are just different UI labels for the same behavior. C) Plan mode lets you discuss and scope changes without executing any code; Build mode actually implements them. D) Build mode runs automated tests; Plan mode generates documentation for the current codebase.
10. Which signal best indicates feature adoption in a Lovable-built product?
A) The number of new lines of code added when implementing the feature. B) Users repeatedly returning to use the feature after their first exposure. C) Users giving positive ratings during initial onboarding interviews. D) The feature being prominently placed on the product's homepage.
