Level 5 exam — No-Code & Automation

Exam — fresh questions

12 original questions to validate Building no-code apps: Bubble, Glide/Softr, forms, ROI, governance.
Answer everything, then click Check: your score and explanations will appear.

5.1 · Recall

1. What are the three pillars of a Bubble app, in order?

Servers, cables, routers Pages (interface), database, «when… then…» workflows Logos, slogans, brochures Screens, colours, fonts

Data → interface → workflows: model first, draw next, connect with logic.

5.1 · Application

2. Lina must handle a multi-department validation circuit with rules. What to choose?

A simple one-off survey Bulk e-mails between departments Bubble (rich business logic, accounts, advanced rules) A shared spreadsheet with no rules

Rich custom logic = Bubble; Glide/Softr to quickly turn a base into a simple app.

5.1 · Arbitration

3. Simple need (directory from a base) but tempted by Bubble «to do it well». Arbitration?

Start with Glide/Softr (fast); Bubble only on a real limitation Bring out Bubble right away to impress Drop the need Recode by hand for six months

Start with the simplest thing that meets the need; Bubble when complexity genuinely demands it.

5.2 · Recall

4. What do Glide and Softr do?

They turn an Airtable/Sheets base into an app (Glide = mobile, Softr = portal) They code in Python for you They print PDFs They are strictly useless

The base acts as the backend, the tool generates the interface; the app follows base changes.

5.2 · Application

5. Lina wants a mobile field app from her partner base. First step?

Draw screens before touching the base Share the raw base with everyone with no rights Delete the base and start over Clean the base (typed fields, relations) then generate the Glide app + rights

Clean base first (the app mirrors it), generation next, rights per department before sharing.

5.3 · Application

6. Files arrive incomplete by e-mail. What does Lina set up?

More bulk e-mails asking people to be careful A spreadsheet where everyone retypes by hand A form (typed, required fields, lists) connected to Airtable + scenario Nothing: manual sorting afterwards is enough

Constrain at input (typed, required, lists, logic) + integration: quality is decided at entry.

5.3 · Application

7. An existing partner should only see the «renewal» questions. Which mechanism?

Send a second paper form Conditional logic (showing based on previous answers) Ask everybody all 40 questions Delete all questions

Only show what is useful based on answers: a relevant, short form with clean data.

5.4 · Recall

8. What is the time-saved formula?

The number of interface colours The boss's feeling on Monday morning There is no method (Duration × frequency) − supervision, plus quality, against costs

The gain lies in repetition (monthly aggregate), not in isolated unit duration.

5.4 · Application

9. Lina compares reminders (frequent, stable, simple) and triage (shifting, costly). Priority?

Launch the shifting triage because it is more impressive Automate nothing on principle Launch both at once with no arbitration Launch reminders; postpone triage until after standardisation

High ROI AND stable AND reasonable first; simplify/standardise before automating the shifting one.

5.4 · Arbitration

10. A salesperson promises a guaranteed quantified gain to sell their automation. Correct stance?

Promise the figure to the director to get the budget Refuse any measurement on the grounds it is complicated Treat the estimate as indicative, measure after one real month before generalising Automate with no supervision or maintenance

No quantified promises: comparable assumptions, real measurement after use, arbitration next.

5.5 · Application

11. A colleague leaves with the scenarios in their head. What does Lina do?

Document each micro-tweak in 20 pages List workflows, record the critical one, name, separate TEST/PROD, export Do nothing and hope nothing breaks Delete all scenarios to start over

Short record per important workflow + naming + TEST/PROD + recovery plan: resumable without her.

5.5 · Arbitration

12. Lina's app will handle sensitive personal data. Arbitration?

Limit rights and collection to the minimum, get validation from IT and a legal counsel before rollout Copy personal data into an uncontrolled shared spreadsheet Ignore the issue because no-code is exempt from law Open all access to the whole company to move fast

Minimal rights, minimised collection, IT/legal (or DPO) validation: this guide gives pointers, not legal advice.

What's next?

Score ≥ 80%: move to Level 6 «In practice» — concrete app cases and toolbox (NO exam).
Score 50-79%: re-read the explanations above — each re-explains the concept — then redo the 48h challenges of the failed sections.
Score < 50%: revisit cards 5.2 (base = backend) and 5.3 (first link), your two vital moves, before continuing.