Level 2 exam — No-Code & Automation

Exam — fresh questions

12 original questions: recall (25%) + application (50%) + arbitration (25%) on relational bases with Airtable.
Answer everything, then click Check: your score and explanations will appear.

2.1 · Recall

1. What is the DNA difference between Notion and Airtable?

Airtable is for writing novels, Notion for calculating Both are word processors Notion = workspace for organizing content, Airtable = relational base for structuring data There is none, they are the same tools

Notion for organizing, Airtable for structuring — the centre of gravity of the need decides.

2.1 · Application

2. Lina has a team wiki AND figures-based files to link. What does she do?

She forces everything into Notion, including calculations She forces everything into Airtable, including documentation She abandons both tools She combines: documentation in Notion, data engine in Airtable

Mixed need = each tool in its zone of excellence, linked by automation if needed.

2.2 · Recall

3. What is the organization hierarchy in Airtable?

Base → tables → typed fields + records Page → blocks → embeds File → tabs → colours Folder → emails → attachments

One base per domain, one table per entity, strictly typed fields, record-files.

2.2 · Application

4. Lina creates the « Échéance » field for her files. What does she choose?

A paper printout of the calendar Date type, to filter and calculate on it Free text to stay flexible Long text with the date handwritten

The strict type (date, currency, select) guarantees clean, filterable and calculable data.

2.2 · Arbitration

5. A colleague suggests putting everything in free text « to go fast ». What does Lina answer?

She accepts: we will structure later, at no cost She deletes the whole base She prints everything to check by eye She refuses: all-text destroys filters and calculations, and restructuring costs ten times more

Typing from the start determines relationships, formulas and views; all-text returns to messy spreadsheet.

2.3 · Application

6. Lina no longer wants to recopy the beneficiary email into each file. What does she create?

A linked record to Bénéficiaires + a lookup bringing back the email A weekly copy-paste A text field recopied by hand A new isolated table per file

Linked record links, lookup brings back a linked value — single fix, propagation everywhere.

2.3 · Recall

7. What is the difference between a lookup and a rollup?

Rollup deletes data, lookup duplicates it Lookup brings back a linked value, rollup aggregates several linked values They are two names for the same thing Lookup prints, rollup translates

Lookup = « fetch and show », rollup = « gather and calculate » — both via a linked record.

2.3 · Arbitration

8. A colleague wants everything in one big table « to simplify ». Verdict?

Good idea: it is simpler and risk-free Accept then print each week Refuse: repeated info, fixes everywhere, inconsistencies — link instead of duplicating Replace with emails

One table = duplication; relational = one piece of info in one place, referenced everywhere.

2.4 · Application

9. Lina wants a Total that calculates itself on each row. Which valid formula?

Print then calculate with a calculator TOTAL? please calculate Type the result by hand in each row {Quantité} * {Prix unitaire}

The formula field calculates in the row from the other fields, with names in braces.

2.4 · Application

10. Lina wants an automatic « En retard » badge. Which valid formula?

IF(AND({Échéance}, {Échéance} < TODAY(), {Statut} != 'Fait'), 'En retard', 'OK') Choose the status by hand each morning Ask each beneficiary by email Stop tracking deadlines

IF + date comparison: the value recalculates itself and drives the filtered « En retard » view.

2.5 · Application

11. Lina's team must steer without touching the base. What does she deliver?

One copy of the base per colleague A dashboard Interface + a form, with the base protected A paper board displayed on the wall The raw base with full edit for everyone

Guided interface for the team, form to collect, raw base protected.

2.5 · Arbitration

12. An external partner must follow progress without seeing internal data. What does Lina do?

She shows nothing and ignores them She prints the whole base each day She shares a read-only view limited to what is needed She sends the full-edit link of the base

Sharing is finely tuned: everyone sees what they should see, the base stays protected.

What's next?

Score ≥ 80%: move to Level 3 — connecting your bases with Make and Zapier (scenarios, triggers, actions).
Score 60-79%: review the missed sections (2.1 arbitration, 2.2 modelling, 2.3 relationships, 2.4 formulas, 2.5 interfaces) and redo the 48h challenges.
Score < 60%: rebuild Lina's base step by step (tables, links, formulas, interface), then retake the test.
In all cases: keep your real base as training ground — one piece of info in one place, calculated, shared minimally.