Level 0 exam — No-Code & Automation

Exam — fresh questions

12 questions to validate the fundamentals: no-code vs low-code, tool overview, process spotting and governance (security, dependence).
Answer everything, then click Check: your score and explanations will appear.

0.1 · Recall

1. What is the difference between no-code and low-code?

No difference No-code = no code; low-code = a little code for advanced cases Low-code is simpler than no-code No-code requires knowing how to code

No-code assembles without code; low-code allows formulas and API calls for advanced cases.

0.1 · Application

2. Lina must copy registrations, calculate a conditional bonus and rebuild invoicing. What is the correct triage?

Everything in no-code Copying in development, invoicing in no-code Everything in development Copying in no-code, calculation in low-code, invoicing in development

Simple and repetitive in no-code, conditional formula in low-code, critical software in development.

0.1 · Arbitration

3. A colleague wants to rebuild the critical payroll software entirely in no-code. What is the verdict?

Great idea, always faster Refuse: outside the area of relevance, critical custom work stays as development Accept if it is free Accept while copying data by hand

No-code unlocks the simple 80%; critical, sensitive custom work stays as development.

0.2 · Application

4. Lina must structure linked registrations (tables, typed fields, filters). Which family should she choose?

App builders alone No family Forms (Tally, Typeform) Databases (Airtable)

You must structure and link: databases like Airtable; forms only collect.

0.2 · Application

5. To track registrations end to end, which coherent stack should she propose?

Tally to collect, Airtable to structure, Make to notify, Notion to document Five app builders in parallel A single diverted workspace for everything Everything in the form, with no base

Each family in its place: collect, structure, connect, organise — linked as a stack.

0.2 · Application

6. Lina hesitates between two automation brands. What should she identify first?

The relevant family (connecting apps), then compare Make, Zapier, n8n The colour of the interface The vendor's country Nothing, draw lots

Family first (connect), brand second; diverting a tool from its zone weakens the system.

0.3 · Recall

7. What is a good automation candidate?

A one-off task never repeated A rare, fuzzy task A repetitive, frequent task with clear rules An expert decision different every time

Repetitive, frequent, clear rule, no subtle human judgement: the ideal quick-win candidate.

0.3 · Application

8. Lina prices: copying (2×20 min/week, simple rule) vs fuzzy report with changing rules. Where to start?

With the fuzzy report, more prestigious With the copying: high impact, low effort, explicit rule With both at the same time With neither, keep everything manual

Quick win first: major time saved and simple; the fuzzy must be clarified before automating.

0.3 · Arbitration

9. A process full of exceptions ("it depends on context") must be automated urgently. What to decide?

Automate it with no trigger or rule Give it to five tools at once Automate it as-is, as fast as possible First clarify and standardise it, then automate the stable part

Automating chaos accelerates chaos: standardise first, then automate the stable part.

0.4 · Recall

10. What are the four no-code risks to know?

Notion, Airtable, Make and Tally Colours, fonts, icons and margins Data security, personal-data compliance, vendor dependence, costs at scale Keyboard, mouse, screen and printer

Security, compliance, vendor lock-in and costs: the four boxes of the governance card.

0.4 · Application

11. Lina connects registrations (names, emails, phones). What is the correct move?

Concentrate everything on one tool with no export Paste the API key in plain text in the scenario Classify sensitivity, check hosting, store the key in the vault, test export, get IT validation Throw the data in without checking

Sensitive data = full governance: sensitivity, hosting, vault, export, IT validation.

0.4 · Arbitration

12. The current tool sharply raises prices and export is impossible. What is the lesson for next time?

Anticipate vendor lock-in: require export, spread the critical, consider self-hosted n8n and keep a plan B Recopy data by hand every day Share the API key to compensate Continue without changing anything

With no export, you are captive: portability, spreading the critical, open source and recovery plan.

What's next?

Score ≥ 80%: move to Level 1 — organise with Notion (pages, blocks, databases, views).
Score between 50% and 80%: review the failed section(s) (0.1 spectrum, 0.2 families, 0.3 framing, 0.4 governance), reread the explanations above, then retake the test.
Score < 50%: reread all of level 0 while applying each 48h challenge (triage card, 4-box stack, framing card, governance card) before retrying.
And next? Keep your three cards (triage, stack, governance): level 1 uses them to build your first Notion space.