Adding Questions

Add one question

Append an object to window.QUESTION_BANK, before the closing ];.

{set:"doctrine", ref:"SEC. 19", q:"When does the right to object not apply?",
 hint:"No right under the DPA is absolute. Say that first.", pts:[
  "It yields where processing rests on a legal obligation.",
  "It yields where processing is necessary to fulfil a contract the subject entered.",
  "Say plainly that no right under the DPA is absolute — that framing scores."
], cite:"Secs. 16(b), 19, RA 10173"},

The fields

← swipe tables sideways

Add a whole set

Two steps.

1. Register the set

Add it to QUESTION_SETS at the top of data/questions.js.

window.QUESTION_SETS = [
  { id:"all",      label:"Full docket" },
  { id:"basics",   label:"Start here" },
  { id:"role",     label:"The role" },
  { id:"doctrine", label:"Doctrine" },
  { id:"enforce",  label:"Enforcement" },
  { id:"build",    label:"Software" },
  { id:"scenario", label:"Scenarios" },
  { id:"fintech",  label:"Fintech" }        // new
];

2. Tag the questions

Give them set:"fintech". The tab, the count, the welcome-screen card, and the filter all appear on their own.

Order in QUESTION_SETS is the order of the tabs and of the welcome picker. Keep "all" first.

Optional: a welcome-screen description

Add a one-line blurb in the BLURB object near the top of assets/js/app.js, keyed by set id. Without one, the card simply shows no description.

var BLURB = {
  basics:  "Plain-language foundations. Start here if privacy is new to you.",
  fintech: "BSP overlay, SIM registration, e-wallet KYC. For a bank or lender."
};

Writing good practice questions

Phrase it the way a person would say it

"Walk me through the breach notification decision" beats "Discuss breach notification requirements." You are rehearsing a conversation, not an exam.

Points, not a script

You will never reproduce a paragraph under pressure, and trying to makes you sound rehearsed. Four to six points you can hit in any order is what a fluent answer is actually made of.

Lead with the framing move

The best answers open with a distinction rather than a fact — "start by saying it is prohibited by default", "do not lead with no". Put that as the first point.

One authority per card

If you cannot name what backs the answer, the question is probably too vague to be useful.

Write hints that reframe, never answer

A good hint says what kind of question this is — "conflict of interest, say the phrase out loud", "three conditions, all required". A bad hint leaks a point from the answer.

Include the trap

Where candidates commonly go wrong, say so in a point: "there is no adequacy regime like the GDPR — a common candidate mistake." Rehearsing the correction is what stops you making it.

Suggested sector sets

Worth building once you know the employer's industry. Sector-specific answers separate a candidate who read the Act from one who understands the job.

Tuning the drill

Near the top of assets/js/app.js.

var MISS_GAP = 3;   // how many cards until a missed question returns
var TARGET   = 90;  // clock turns amber here
var LONG     = 150; // clock turns red here

• Lower MISS_GAP to hammer weak areas harder.
• Lower TARGET if a recruiter screens you first — those calls move faster and reward tighter answers.

Keyboard shortcuts