[ { "id": 1, "category": "Personal Data", "difficulty": "Beginner", "type": "single", "question": "Which item is personal data when linked to an identifiable person?", "options": [ "A random weather reading", "An employee identification number", "A public holiday date", "A generic product code" ], "answers": [ 1 ], "explanation": "An employee identification number can single out a specific worker.", "principle": "Identifiability", "risk": "Unnecessary exposure can reveal a person’s identity.", "saferAction": "Treat identifiers as personal data and restrict access." }, { "id": 2, "category": "Personal Data", "difficulty": "Beginner", "type": "multi", "question": "Which items can be indirect identifiers? Select all that apply.", "options": [ "Exact location history", "Date of birth", "Favourite colour alone", "Device advertising identifier" ], "answers": [ 0, 1, 3 ], "explanation": "Several indirect identifiers can identify someone alone or when combined.", "principle": "Identifiability", "risk": "Combined data can re-identify people unexpectedly.", "saferAction": "Assess datasets for singling-out and combination risks." }, { "id": 3, "category": "Personal Data", "difficulty": "Intermediate", "type": "single", "question": "A customer list contains names and purchase dates. What is it?", "options": [ "Anonymous statistical data", "Personal data", "Public-domain data only", "Non-personal operational data" ], "answers": [ 1 ], "explanation": "Names directly identify customers, so the list is personal data.", "principle": "Data classification", "risk": "Misclassification can remove necessary protections.", "saferAction": "Classify and protect the list as personal data." }, { "id": 4, "category": "Personal Data", "difficulty": "Intermediate", "type": "truefalse", "question": "A work email address can be personal data.", "options": [ "True", "False" ], "answers": [ 0 ], "explanation": "A work email often identifies a named employee.", "principle": "Identifiability", "risk": "Public visibility does not remove privacy obligations.", "saferAction": "Use work contact data only for appropriate purposes." }, { "id": 5, "category": "Personal Data", "difficulty": "Advanced", "type": "single", "question": "Which test best determines whether information is anonymous?", "options": [ "Whether names were removed", "Whether re-identification is reasonably likely", "Whether the file is encrypted", "Whether users agreed to sharing" ], "answers": [ 1 ], "explanation": "Anonymous data must resist reasonably likely identification methods.", "principle": "Anonymization", "risk": "Removing names alone may leave strong identifiers.", "saferAction": "Evaluate realistic re-identification routes before release." }, { "id": 6, "category": "Personal Data", "difficulty": "Advanced", "type": "scenario", "question": "A dataset has age, postcode, gender, and job title but no names. What is the best conclusion?", "options": [ "It is automatically anonymous", "It may still identify people through combinations", "It is always sensitive data", "It is safe to publish without review" ], "answers": [ 1 ], "explanation": "Combinations of quasi-identifiers can identify individuals.", "principle": "Re-identification risk", "risk": "Rare combinations can expose specific people.", "saferAction": "Perform a re-identification assessment and generalize fields." }, { "id": 7, "category": "Sensitive Data", "difficulty": "Beginner", "type": "single", "question": "Which information normally requires stronger protection?", "options": [ "Office opening hours", "Biometric templates", "Product catalogue numbers", "Anonymous traffic counts" ], "answers": [ 1 ], "explanation": "Biometric templates can uniquely identify individuals and are highly sensitive.", "principle": "Special-category data", "risk": "Biometric compromise can be difficult to reverse.", "saferAction": "Use strict access, encryption, and limited purposes." }, { "id": 8, "category": "Sensitive Data", "difficulty": "Beginner", "type": "multi", "question": "Which are commonly sensitive categories? Select all that apply.", "options": [ "Health records", "Religious beliefs", "Preferred font size", "Genetic information" ], "answers": [ 0, 1, 3 ], "explanation": "Health, religion, and genetic information can create serious harm if misused.", "principle": "Sensitive data", "risk": "Misuse can cause discrimination or exclusion.", "saferAction": "Collect only when justified and apply stronger safeguards." }, { "id": 9, "category": "Sensitive Data", "difficulty": "Intermediate", "type": "single", "question": "Why is a password hash still security-sensitive?", "options": [ "It always reveals the password instantly", "It can support account attacks if stolen", "It is not data", "It becomes public after hashing" ], "answers": [ 1 ], "explanation": "Weak or stolen hashes may enable password cracking and account compromise.", "principle": "Security of credentials", "risk": "Credential theft can lead to unauthorized access.", "saferAction": "Use strong hashing, salts, and access controls." }, { "id": 10, "category": "Sensitive Data", "difficulty": "Intermediate", "type": "truefalse", "question": "Publicly posted health information can still deserve privacy protection.", "options": [ "True", "False" ], "answers": [ 0 ], "explanation": "Public availability does not automatically remove privacy risks or obligations.", "principle": "Contextual privacy", "risk": "Reuse can amplify harm beyond the original context.", "saferAction": "Check lawful purpose, fairness, and user expectations." }, { "id": 11, "category": "Sensitive Data", "difficulty": "Advanced", "type": "scenario", "question": "A fitness app wants precise heart-rate data for personalized advertisements. What is the strongest concern?", "options": [ "Screen size", "Sensitive-data profiling for an unrelated purpose", "Database naming", "Logo design" ], "answers": [ 1 ], "explanation": "Health-related data used for advertising raises purpose, consent, and fairness concerns.", "principle": "Purpose limitation", "risk": "Sensitive profiling can manipulate or discriminate.", "saferAction": "Separate essential health processing from optional advertising." }, { "id": 12, "category": "Sensitive Data", "difficulty": "Advanced", "type": "single", "question": "Which safeguard best reduces insider access to medical records?", "options": [ "Shared administrator account", "Role-based least-privilege access with audit logs", "Posting files in a team chat", "Disabling authentication" ], "answers": [ 1 ], "explanation": "Least privilege and auditing reduce unauthorized internal access.", "principle": "Access control", "risk": "Insiders may browse records without business need.", "saferAction": "Limit access by role and review logs regularly." }, { "id": 13, "category": "Consent", "difficulty": "Beginner", "type": "single", "question": "Valid consent should be:", "options": [ "Forced and bundled", "Freely given, specific, informed, and unambiguous", "Hidden in a long policy", "Permanent and impossible to withdraw" ], "answers": [ 1 ], "explanation": "Consent must reflect a genuine, informed choice.", "principle": "Valid consent", "risk": "Invalid consent can make processing unlawful.", "saferAction": "Use clear choices and an easy withdrawal method." }, { "id": 14, "category": "Consent", "difficulty": "Beginner", "type": "truefalse", "question": "Pre-ticked marketing boxes usually demonstrate active consent.", "options": [ "True", "False" ], "answers": [ 1 ], "explanation": "Pre-ticked boxes do not show a clear affirmative action.", "principle": "Affirmative consent", "risk": "Users may be enrolled without real choice.", "saferAction": "Leave optional boxes unticked by default." }, { "id": 15, "category": "Consent", "difficulty": "Intermediate", "type": "scenario", "question": "A service requires advertising consent to access an essential feature. What is the main issue?", "options": [ "The font is small", "Consent may not be freely given", "The database is slow", "The privacy notice is too short" ], "answers": [ 1 ], "explanation": "Bundling optional advertising with an essential service can remove real choice.", "principle": "Freely given consent", "risk": "Users may be coerced into unrelated processing.", "saferAction": "Offer the service without optional advertising consent." }, { "id": 16, "category": "Consent", "difficulty": "Intermediate", "type": "multi", "question": "Which records help demonstrate consent? Select all that apply.", "options": [ "Who consented", "What they were told", "When and how consent occurred", "Their unrelated browsing history" ], "answers": [ 0, 1, 2 ], "explanation": "Organizations should record the consent event and the notice presented.", "principle": "Accountability", "risk": "Poor records make consent difficult to prove.", "saferAction": "Store minimal consent evidence and notice versions." }, { "id": 17, "category": "Consent", "difficulty": "Advanced", "type": "single", "question": "When should consent be refreshed?", "options": [ "Never", "When purposes or processing materially change", "Every time a page loads", "Only after a breach" ], "answers": [ 1 ], "explanation": "Material changes can invalidate the scope of earlier consent.", "principle": "Specific consent", "risk": "Old consent may not cover new processing.", "saferAction": "Notify users and obtain a new valid choice." }, { "id": 18, "category": "Consent", "difficulty": "Advanced", "type": "scenario", "question": "A user withdraws analytics consent. What should happen next?", "options": [ "Continue collecting secretly", "Stop consent-based collection and update preferences", "Delete the entire service account automatically", "Ignore the request for thirty days" ], "answers": [ 1 ], "explanation": "Withdrawal should be as easy and effective as giving consent.", "principle": "Withdrawal", "risk": "Continued tracking may be unlawful and unexpected.", "saferAction": "Stop future consent-based analytics promptly." }, { "id": 19, "category": "Lawful Processing", "difficulty": "Beginner", "type": "single", "question": "Before processing personal data, an organization should identify:", "options": [ "A lawful basis", "A favourite colour", "A social-media slogan", "A larger monitor" ], "answers": [ 0 ], "explanation": "Processing needs a valid legal justification.", "principle": "Lawfulness", "risk": "Unsupported processing can violate privacy law.", "saferAction": "Document the lawful basis before collection." }, { "id": 20, "category": "Lawful Processing", "difficulty": "Beginner", "type": "single", "question": "Which basis may support delivering a product a customer ordered?", "options": [ "Contract necessity", "Curiosity", "Public popularity", "Unlimited consent" ], "answers": [ 0 ], "explanation": "Processing delivery details may be necessary to perform the contract.", "principle": "Contract necessity", "risk": "Using more data than needed exceeds the purpose.", "saferAction": "Limit processing to order fulfilment needs." }, { "id": 21, "category": "Lawful Processing", "difficulty": "Intermediate", "type": "scenario", "question": "A company claims legitimate interests for employee surveillance. What must it do?", "options": [ "Skip all assessment", "Balance necessity against employee rights", "Hide monitoring completely", "Collect every available signal" ], "answers": [ 1 ], "explanation": "Legitimate interests require necessity and a balancing assessment.", "principle": "Legitimate interests", "risk": "Intrusive monitoring can unfairly harm workers.", "saferAction": "Document necessity, proportionality, and safeguards." }, { "id": 22, "category": "Lawful Processing", "difficulty": "Intermediate", "type": "truefalse", "question": "A lawful basis can be selected after processing starts without review.", "options": [ "True", "False" ], "answers": [ 1 ], "explanation": "The legal basis should be established before processing begins.", "principle": "Accountability", "risk": "Retroactive justification can hide unlawful collection.", "saferAction": "Complete a lawful-basis assessment in advance." }, { "id": 23, "category": "Lawful Processing", "difficulty": "Advanced", "type": "single", "question": "Which statement about consent is correct?", "options": [ "Consent is always the best lawful basis", "Consent is one possible basis and must fit the relationship", "Consent overrides every privacy principle", "Consent permits unlimited future use" ], "answers": [ 1 ], "explanation": "Consent is not automatically appropriate, especially where power is unequal.", "principle": "Appropriate lawful basis", "risk": "Misusing consent can create false legitimacy.", "saferAction": "Choose the basis that accurately matches the processing." }, { "id": 24, "category": "Lawful Processing", "difficulty": "Advanced", "type": "scenario", "question": "A hospital processes emergency information for an unconscious patient. What is most relevant?", "options": [ "Only marketing consent", "A legal basis supporting vital or health-related needs", "A cookie banner", "A loyalty programme" ], "answers": [ 1 ], "explanation": "Emergency processing may rely on bases designed for vital or healthcare needs.", "principle": "Vital interests", "risk": "Delays can endanger the patient, while excess use harms privacy.", "saferAction": "Process only what the emergency requires and document it." }, { "id": 25, "category": "Data Minimization", "difficulty": "Beginner", "type": "single", "question": "Data minimization means collecting:", "options": [ "Every available detail", "Only data necessary for the stated purpose", "Data with the longest retention", "Only public information" ], "answers": [ 1 ], "explanation": "Organizations should limit collection to relevant and necessary data.", "principle": "Data minimization", "risk": "Excess data increases breach and misuse risks.", "saferAction": "Remove fields that do not support the purpose." }, { "id": 26, "category": "Data Minimization", "difficulty": "Beginner", "type": "scenario", "question": "A newsletter form asks for passport number. What should be done?", "options": [ "Keep it for future uses", "Remove the passport field", "Make it mandatory", "Publish it" ], "answers": [ 1 ], "explanation": "A passport number is unnecessary for ordinary newsletter delivery.", "principle": "Necessity", "risk": "Overcollection creates disproportionate identity risks.", "saferAction": "Collect only an email address and needed preferences." }, { "id": 27, "category": "Data Minimization", "difficulty": "Intermediate", "type": "multi", "question": "Which practices support minimization? Select all that apply.", "options": [ "Optional fields disabled by default", "Short retention periods", "Collecting full birthdates for age bands", "Aggregating reports" ], "answers": [ 0, 1, 3 ], "explanation": "Default reduction, limited retention, and aggregation reduce exposure.", "principle": "Data minimization", "risk": "Detailed records create larger attack and misuse surfaces.", "saferAction": "Use the least detailed data that meets the need." }, { "id": 28, "category": "Data Minimization", "difficulty": "Intermediate", "type": "truefalse", "question": "Keeping unused columns is harmless when storage is cheap.", "options": [ "True", "False" ], "answers": [ 1 ], "explanation": "Storage cost does not remove privacy and security risks.", "principle": "Data minimization", "risk": "Unused data can still be breached or repurposed.", "saferAction": "Delete or avoid collecting unused fields." }, { "id": 29, "category": "Data Minimization", "difficulty": "Advanced", "type": "single", "question": "A fraud model needs age bands, not exact birthdates. What should be stored?", "options": [ "Exact birthdates forever", "The minimum age band needed", "Passport scans", "Family medical history" ], "answers": [ 1 ], "explanation": "Age bands satisfy the purpose with less identifying detail.", "principle": "Proportionality", "risk": "Exact dates increase identity and profiling risks.", "saferAction": "Transform to bands and discard unnecessary precision." }, { "id": 30, "category": "Data Minimization", "difficulty": "Advanced", "type": "scenario", "question": "Support agents can view full payment cards, although they only need last four digits. Best fix?", "options": [ "Increase monitor size", "Mask card numbers and restrict full access", "Email card data", "Copy cards into notes" ], "answers": [ 1 ], "explanation": "Displaying only necessary digits reduces exposure.", "principle": "Least privilege", "risk": "Excess visibility raises insider and shoulder-surfing risks.", "saferAction": "Mask values and reserve full access for exceptional roles." }, { "id": 31, "category": "Purpose Limitation", "difficulty": "Beginner", "type": "single", "question": "Purpose limitation requires data to be used for:", "options": [ "Any profitable idea", "Specified and compatible purposes", "Unlimited internal experiments", "Secret future plans" ], "answers": [ 1 ], "explanation": "People should understand why data is collected and how it will be used.", "principle": "Purpose limitation", "risk": "Unexpected reuse can be unfair and unlawful.", "saferAction": "Define purposes clearly before collection." }, { "id": 32, "category": "Purpose Limitation", "difficulty": "Beginner", "type": "scenario", "question": "Delivery addresses are reused for political advertising. Main concern?", "options": [ "Colour contrast", "Incompatible secondary use", "Printer speed", "File naming" ], "answers": [ 1 ], "explanation": "Political advertising is unrelated to delivering an order.", "principle": "Purpose limitation", "risk": "Unexpected profiling can manipulate or expose people.", "saferAction": "Assess compatibility and obtain a valid basis before reuse." }, { "id": 33, "category": "Purpose Limitation", "difficulty": "Intermediate", "type": "truefalse", "question": "A broad phrase like “for business purposes” always provides a specific purpose.", "options": [ "True", "False" ], "answers": [ 1 ], "explanation": "Vague purposes do not meaningfully inform people.", "principle": "Transparency", "risk": "Broad wording can conceal extensive reuse.", "saferAction": "Describe concrete purposes in plain language." }, { "id": 34, "category": "Purpose Limitation", "difficulty": "Intermediate", "type": "multi", "question": "When assessing a new purpose, consider: Select all that apply.", "options": [ "Connection to the original purpose", "User expectations", "Possible consequences", "Office furniture" ], "answers": [ 0, 1, 2 ], "explanation": "Compatibility depends on context, expectations, and impact.", "principle": "Compatible use", "risk": "A surprising new use may create unfair harm.", "saferAction": "Perform and document a compatibility assessment." }, { "id": 35, "category": "Purpose Limitation", "difficulty": "Advanced", "type": "single", "question": "Which design best supports purpose separation?", "options": [ "One unrestricted data lake", "Separate datasets and permissions by purpose", "Shared passwords", "Permanent exports" ], "answers": [ 1 ], "explanation": "Technical separation helps prevent unauthorized cross-purpose use.", "principle": "Privacy by design", "risk": "Broad access encourages function creep.", "saferAction": "Segment data, access, and retention by purpose." }, { "id": 36, "category": "Purpose Limitation", "difficulty": "Advanced", "type": "scenario", "question": "Researchers want to use service logs for a new study. What is the best first step?", "options": [ "Publish immediately", "Assess compatibility, lawful basis, necessity, and safeguards", "Ignore the original notice", "Add more identifiers" ], "answers": [ 1 ], "explanation": "New research use needs a structured privacy assessment.", "principle": "Purpose assessment", "risk": "Logs may contain identifiers and sensitive behaviour.", "saferAction": "Minimize, pseudonymize, and document the research basis." }, { "id": 37, "category": "Retention", "difficulty": "Beginner", "type": "single", "question": "A retention schedule should define:", "options": [ "How long data is kept and why", "Only the database name", "Employee lunch times", "Website colours" ], "answers": [ 0 ], "explanation": "Retention should be tied to purpose and legal obligations.", "principle": "Storage limitation", "risk": "Indefinite storage increases risk and cost.", "saferAction": "Set and enforce documented deletion periods." }, { "id": 38, "category": "Retention", "difficulty": "Beginner", "type": "truefalse", "question": "Personal data should be kept forever in case it becomes useful.", "options": [ "True", "False" ], "answers": [ 1 ], "explanation": "Speculative future usefulness is not a valid retention strategy.", "principle": "Storage limitation", "risk": "Old data can be breached or misused.", "saferAction": "Delete or anonymize data when no longer needed." }, { "id": 39, "category": "Retention", "difficulty": "Intermediate", "type": "scenario", "question": "Job applications from unsuccessful candidates remain indefinitely. Best action?", "options": [ "Keep every application forever", "Apply a justified retention period and delete afterward", "Post applications publicly", "Move them to personal laptops" ], "answers": [ 1 ], "explanation": "Recruitment records should not outlive their justified need.", "principle": "Retention", "risk": "Old applicant data creates continuing exposure.", "saferAction": "Automate deletion after the approved period." }, { "id": 40, "category": "Retention", "difficulty": "Intermediate", "type": "multi", "question": "Which can justify retention? Select all that apply.", "options": [ "Active contract needs", "Legal recordkeeping duties", "Unspecified future marketing", "Defending current legal claims" ], "answers": [ 0, 1, 3 ], "explanation": "Retention should connect to concrete operational or legal needs.", "principle": "Storage limitation", "risk": "Vague reasons lead to excessive storage.", "saferAction": "Record the reason and expiry rule for each dataset." }, { "id": 41, "category": "Retention", "difficulty": "Advanced", "type": "single", "question": "What is the best approach to backups after a deletion request?", "options": [ "Pretend backups do not exist", "Prevent restored data from returning to active use and expire backups normally", "Publish the backups", "Keep active copies forever" ], "answers": [ 1 ], "explanation": "Deletion processes should account for backup cycles and restoration controls.", "principle": "Deletion lifecycle", "risk": "Deleted data may reappear after recovery.", "saferAction": "Flag deletions and ensure backups expire securely." }, { "id": 42, "category": "Retention", "difficulty": "Advanced", "type": "scenario", "question": "A legal hold applies to selected records. What should happen?", "options": [ "Delete everything immediately", "Suspend deletion only for relevant records and document the hold", "Keep all company data forever", "Disable access logs" ], "answers": [ 1 ], "explanation": "Legal holds should be targeted and controlled.", "principle": "Accountability", "risk": "Overbroad holds defeat storage limitation.", "saferAction": "Scope, review, and release the hold when justified." }, { "id": 43, "category": "Anonymization & Pseudonymization", "difficulty": "Beginner", "type": "single", "question": "Pseudonymization replaces direct identifiers with:", "options": [ "A code or token linked separately", "A public name list", "No protection", "A marketing label" ], "answers": [ 0 ], "explanation": "Pseudonyms reduce direct identification but can remain reversible.", "principle": "Pseudonymization", "risk": "Linkage keys can re-identify people.", "saferAction": "Separate and strongly protect the re-identification key." }, { "id": 44, "category": "Anonymization & Pseudonymization", "difficulty": "Beginner", "type": "truefalse", "question": "Pseudonymized data is always anonymous.", "options": [ "True", "False" ], "answers": [ 1 ], "explanation": "Pseudonymized data remains personal when re-identification is possible.", "principle": "Data classification", "risk": "False anonymity assumptions weaken safeguards.", "saferAction": "Continue applying personal-data protections." }, { "id": 45, "category": "Anonymization & Pseudonymization", "difficulty": "Intermediate", "type": "single", "question": "Which technique reduces uniqueness in a location dataset?", "options": [ "Increasing coordinate precision", "Generalizing locations into larger regions", "Adding names", "Publishing device identifiers" ], "answers": [ 1 ], "explanation": "Generalization lowers the chance that rare locations identify someone.", "principle": "Anonymization", "risk": "Precise movement patterns are highly identifying.", "saferAction": "Reduce spatial and temporal precision." }, { "id": 46, "category": "Anonymization & Pseudonymization", "difficulty": "Intermediate", "type": "multi", "question": "Which can cause re-identification? Select all that apply.", "options": [ "Rare combinations", "External datasets", "Persistent identifiers", "Removing column headings" ], "answers": [ 0, 1, 2 ], "explanation": "Uniqueness, linkage, and stable identifiers can expose identities.", "principle": "Re-identification risk", "risk": "Released datasets may be linked with outside sources.", "saferAction": "Test realistic linkage attacks before release." }, { "id": 47, "category": "Anonymization & Pseudonymization", "difficulty": "Advanced", "type": "scenario", "question": "A public dataset removes names but keeps exact timestamps and routes. Best assessment?", "options": [ "Safely anonymous", "High re-identification risk", "Not personal because names are gone", "Safe if compressed" ], "answers": [ 1 ], "explanation": "Mobility traces can uniquely identify individuals.", "principle": "Anonymization", "risk": "Routes may reveal homes, workplaces, or sensitive visits.", "saferAction": "Aggregate, generalize, and validate anonymity." }, { "id": 48, "category": "Anonymization & Pseudonymization", "difficulty": "Advanced", "type": "single", "question": "What distinguishes anonymization from encryption?", "options": [ "Anonymization aims to prevent identification; encryption controls access", "They are identical", "Encryption deletes data", "Anonymization requires passwords" ], "answers": [ 0 ], "explanation": "Encryption is reversible with a key, while robust anonymization aims to remove identifiability.", "principle": "Privacy engineering", "risk": "Confusing controls can lead to unsafe disclosure.", "saferAction": "Use each technique for its intended risk." }, { "id": 49, "category": "Encryption & Access", "difficulty": "Beginner", "type": "single", "question": "Encryption in transit protects data while it is:", "options": [ "Moving across networks", "Printed on paper", "Deleted", "Aggregated" ], "answers": [ 0 ], "explanation": "Transport encryption reduces interception risk.", "principle": "Encryption", "risk": "Attackers may read unprotected network traffic.", "saferAction": "Use modern secure transport protocols." }, { "id": 50, "category": "Encryption & Access", "difficulty": "Beginner", "type": "single", "question": "Least privilege means users receive:", "options": [ "All available permissions", "Only access needed for their role", "Shared administrator access", "Permanent access after leaving" ], "answers": [ 1 ], "explanation": "Least privilege limits access to necessary tasks.", "principle": "Access control", "risk": "Excess permissions increase misuse and breach impact.", "saferAction": "Grant minimal access and review it regularly." }, { "id": 51, "category": "Encryption & Access", "difficulty": "Intermediate", "type": "multi", "question": "Which controls strengthen account security? Select all that apply.", "options": [ "Multifactor authentication", "Unique accounts", "Shared passwords", "Periodic access reviews" ], "answers": [ 0, 1, 3 ], "explanation": "Strong authentication and accountability reduce unauthorized access.", "principle": "Access security", "risk": "Shared credentials prevent traceability.", "saferAction": "Use individual accounts, MFA, and reviews." }, { "id": 52, "category": "Encryption & Access", "difficulty": "Intermediate", "type": "truefalse", "question": "Encryption removes the need for access controls.", "options": [ "True", "False" ], "answers": [ 1 ], "explanation": "Authorized systems can decrypt data, so access controls remain essential.", "principle": "Defense in depth", "risk": "An authorized but malicious user may still misuse data.", "saferAction": "Combine encryption with permissions and monitoring." }, { "id": 53, "category": "Encryption & Access", "difficulty": "Advanced", "type": "scenario", "question": "A former employee still accesses customer records. What failed?", "options": [ "Colour management", "Timely access revocation", "Data compression", "Cookie design" ], "answers": [ 1 ], "explanation": "Offboarding should promptly remove accounts and permissions.", "principle": "Identity lifecycle", "risk": "Dormant access can enable unauthorized disclosure.", "saferAction": "Automate revocation and verify completion." }, { "id": 54, "category": "Encryption & Access", "difficulty": "Advanced", "type": "single", "question": "Where should encryption keys be stored?", "options": [ "Beside encrypted data in plain text", "In a controlled key-management system", "In public source code", "In shared chat messages" ], "answers": [ 1 ], "explanation": "Separate key management protects encrypted data from a single-point compromise.", "principle": "Key management", "risk": "Stolen keys can neutralize encryption.", "saferAction": "Use managed keys, rotation, and strict access." }, { "id": 55, "category": "Data Subject Rights", "difficulty": "Beginner", "type": "single", "question": "An access request generally asks an organization to:", "options": [ "Provide information about personal data it holds", "Delete every database", "Reveal other people’s records", "Publish passwords" ], "answers": [ 0 ], "explanation": "People may request access to their own data and processing information.", "principle": "Access right", "risk": "Poor identity checks can expose another person’s data.", "saferAction": "Verify identity proportionately before disclosure." }, { "id": 56, "category": "Data Subject Rights", "difficulty": "Beginner", "type": "single", "question": "The correction right helps people fix:", "options": [ "Inaccurate personal data", "Website colours", "Company profits", "Anonymous statistics only" ], "answers": [ 0 ], "explanation": "Accurate records reduce unfair decisions and harm.", "principle": "Accuracy", "risk": "Incorrect data can cause denial or misclassification.", "saferAction": "Provide a clear correction process." }, { "id": 57, "category": "Data Subject Rights", "difficulty": "Intermediate", "type": "scenario", "question": "A user requests deletion, but tax law requires some invoices. Best response?", "options": [ "Delete legally required records", "Keep only required records, explain the limit, and delete the rest", "Ignore the user", "Keep all data indefinitely" ], "answers": [ 1 ], "explanation": "Deletion rights can have lawful exceptions that should be narrowly applied.", "principle": "Erasure", "risk": "Over-retention or unlawful deletion can both create risk.", "saferAction": "Document the exception and restrict retained records." }, { "id": 58, "category": "Data Subject Rights", "difficulty": "Intermediate", "type": "multi", "question": "A good rights-request workflow includes: Select all that apply.", "options": [ "Request logging", "Identity verification", "Deadline tracking", "Sending data to any requester" ], "answers": [ 0, 1, 2 ], "explanation": "Structured workflows improve security and timely compliance.", "principle": "Accountability", "risk": "Requests may be lost, delayed, or disclosed incorrectly.", "saferAction": "Track, verify, search, review, and respond securely." }, { "id": 59, "category": "Data Subject Rights", "difficulty": "Advanced", "type": "single", "question": "Why should identity verification be proportionate?", "options": [ "To collect more data", "To avoid demanding excessive information while preventing fraud", "To delay every request", "To publish identities" ], "answers": [ 1 ], "explanation": "Verification should match the disclosure risk without overcollection.", "principle": "Data minimization", "risk": "Excessive checks can create new privacy risks.", "saferAction": "Use the least intrusive reliable verification method." }, { "id": 60, "category": "Data Subject Rights", "difficulty": "Advanced", "type": "scenario", "question": "An export includes another customer’s support messages. What is the issue?", "options": [ "Correct access response", "Third-party disclosure during rights fulfilment", "Good anonymization", "Required transparency" ], "answers": [ 1 ], "explanation": "Access responses must protect the rights of other people.", "principle": "Confidentiality", "risk": "A rights process can itself cause a breach.", "saferAction": "Review and redact third-party information before release." }, { "id": 61, "category": "Cookies & Tracking", "difficulty": "Beginner", "type": "single", "question": "Which cookies are most likely essential?", "options": [ "Session authentication cookies", "Cross-site advertising cookies", "Optional analytics cookies", "Behavioural profiling cookies" ], "answers": [ 0 ], "explanation": "Authentication cookies can be necessary for a requested service.", "principle": "Necessity", "risk": "Mislabeling optional tracking as essential removes choice.", "saferAction": "Classify cookies by actual function." }, { "id": 62, "category": "Cookies & Tracking", "difficulty": "Beginner", "type": "truefalse", "question": "Rejecting optional cookies should be as easy as accepting them.", "options": [ "True", "False" ], "answers": [ 0 ], "explanation": "Balanced choices support genuine user control.", "principle": "Fair choice", "risk": "Dark patterns can manipulate users into tracking.", "saferAction": "Provide equally prominent accept and reject controls." }, { "id": 63, "category": "Cookies & Tracking", "difficulty": "Intermediate", "type": "scenario", "question": "A website loads advertising trackers before consent. Main issue?", "options": [ "The banner colour", "Tracking begins before a valid choice", "The page is responsive", "The logo is missing" ], "answers": [ 1 ], "explanation": "Optional trackers should not start before the required permission.", "principle": "Prior consent", "risk": "Users are tracked despite declining or not choosing.", "saferAction": "Block optional tags until consent is recorded." }, { "id": 64, "category": "Cookies & Tracking", "difficulty": "Intermediate", "type": "multi", "question": "A useful cookie notice should explain: Select all that apply.", "options": [ "Cookie purposes", "Providers", "Durations", "Unrelated employee salaries" ], "answers": [ 0, 1, 2 ], "explanation": "Users need meaningful information to make tracking choices.", "principle": "Transparency", "risk": "Vague notices hide the scale of tracking.", "saferAction": "List categories, purposes, providers, and lifetimes." }, { "id": 65, "category": "Cookies & Tracking", "difficulty": "Advanced", "type": "single", "question": "Browser fingerprinting is privacy-relevant because it can:", "options": [ "Identify or link devices without traditional cookies", "Improve keyboard layout only", "Delete accounts", "Encrypt databases" ], "answers": [ 0 ], "explanation": "Fingerprinting combines device signals to recognize users.", "principle": "Tracking transparency", "risk": "Users may be tracked without clear controls.", "saferAction": "Assess necessity, disclose it, and provide lawful controls." }, { "id": 66, "category": "Cookies & Tracking", "difficulty": "Advanced", "type": "scenario", "question": "A user rejects analytics, but server logs still build behavioural profiles. Best conclusion?", "options": [ "Consent choice is respected", "The organization may be bypassing the user’s choice", "Logs are never personal", "Profiling is always essential" ], "answers": [ 1 ], "explanation": "Changing the tracking method does not remove the underlying privacy issue.", "principle": "User choice", "risk": "Hidden profiling undermines trust and consent.", "saferAction": "Stop non-essential profiling across all technologies." }, { "id": 67, "category": "Third-Party Sharing", "difficulty": "Beginner", "type": "single", "question": "Before sharing data with a vendor, an organization should:", "options": [ "Assess necessity, safeguards, and responsibilities", "Send the entire database", "Share passwords", "Skip contracts" ], "answers": [ 0 ], "explanation": "Vendor use should be controlled and documented.", "principle": "Processor management", "risk": "Vendors can expand breach and misuse risks.", "saferAction": "Complete due diligence and a suitable agreement." }, { "id": 68, "category": "Third-Party Sharing", "difficulty": "Beginner", "type": "truefalse", "question": "A vendor may use customer data for any purpose because it stores the data.", "options": [ "True", "False" ], "answers": [ 1 ], "explanation": "A processor should act only on documented instructions unless law requires otherwise.", "principle": "Purpose control", "risk": "Unauthorized vendor reuse can harm customers.", "saferAction": "Restrict processing purposes contractually and technically." }, { "id": 69, "category": "Third-Party Sharing", "difficulty": "Intermediate", "type": "multi", "question": "Vendor due diligence should consider: Select all that apply.", "options": [ "Security controls", "Subprocessors", "Breach history", "Office paint colour" ], "answers": [ 0, 1, 2 ], "explanation": "Security posture, supply chains, and incident history affect risk.", "principle": "Third-party risk", "risk": "Weak vendors can expose large datasets.", "saferAction": "Assess vendors before onboarding and periodically afterward." }, { "id": 70, "category": "Third-Party Sharing", "difficulty": "Intermediate", "type": "scenario", "question": "A marketing vendor requests all customer records for a small campaign. Best response?", "options": [ "Share everything", "Provide only necessary fields for selected recipients", "Give administrator credentials", "Upload to a public link" ], "answers": [ 1 ], "explanation": "Sharing should be minimized to the campaign’s actual need.", "principle": "Data minimization", "risk": "Bulk disclosure increases misuse and breach impact.", "saferAction": "Filter records and fields before secure transfer." }, { "id": 71, "category": "Third-Party Sharing", "difficulty": "Advanced", "type": "single", "question": "What should happen when a vendor contract ends?", "options": [ "Vendor keeps all copies forever", "Return or securely delete data and confirm completion", "Data becomes public", "Access remains active" ], "answers": [ 1 ], "explanation": "End-of-service procedures should close access and remove retained copies.", "principle": "Lifecycle management", "risk": "Residual copies can be breached later.", "saferAction": "Revoke access and obtain deletion confirmation." }, { "id": 72, "category": "Third-Party Sharing", "difficulty": "Advanced", "type": "scenario", "question": "A vendor adds an overseas subprocessor without notice. What should the organization review?", "options": [ "Only invoice formatting", "Contract terms, transfer safeguards, security, and authorization", "Office parking", "Logo placement" ], "answers": [ 1 ], "explanation": "New subprocessors can change security and transfer risks.", "principle": "Supply-chain governance", "risk": "Unreviewed transfers may violate obligations.", "saferAction": "Require notice, assessment, and approval controls." }, { "id": 73, "category": "Cross-Border Transfers", "difficulty": "Beginner", "type": "single", "question": "A cross-border transfer occurs when personal data is:", "options": [ "Accessed or sent from another jurisdiction", "Printed locally", "Deleted securely", "Stored in the same approved location" ], "answers": [ 0 ], "explanation": "Remote access from another country may count as a transfer.", "principle": "International transfers", "risk": "Different jurisdictions may provide different protections.", "saferAction": "Map data locations and remote access." }, { "id": 74, "category": "Cross-Border Transfers", "difficulty": "Beginner", "type": "truefalse", "question": "Cloud storage location is irrelevant to privacy compliance.", "options": [ "True", "False" ], "answers": [ 1 ], "explanation": "Storage and access locations can trigger transfer requirements.", "principle": "Data location", "risk": "Unknown locations can create unlawful transfers.", "saferAction": "Maintain an accurate data-location inventory." }, { "id": 75, "category": "Cross-Border Transfers", "difficulty": "Intermediate", "type": "single", "question": "A transfer assessment should evaluate:", "options": [ "Destination protections and practical risks", "Only internet speed", "Brand colours", "Printer models" ], "answers": [ 0 ], "explanation": "Organizations should assess whether transferred data receives effective protection.", "principle": "Transfer risk", "risk": "Government access or weak remedies may increase risk.", "saferAction": "Document destination risks and supplementary safeguards." }, { "id": 76, "category": "Cross-Border Transfers", "difficulty": "Intermediate", "type": "multi", "question": "Possible transfer safeguards include: Select all that apply.", "options": [ "Approved contractual clauses", "Encryption with controlled keys", "Data minimization", "Public posting" ], "answers": [ 0, 1, 2 ], "explanation": "Legal, technical, and organizational safeguards can work together.", "principle": "Transfer safeguards", "risk": "A single paper control may not address practical risks.", "saferAction": "Combine suitable legal terms with strong technical controls." }, { "id": 77, "category": "Cross-Border Transfers", "difficulty": "Advanced", "type": "scenario", "question": "Foreign support staff can remotely view customer records. What should be assessed?", "options": [ "Only their keyboard", "Whether remote access is a regulated transfer and adequately protected", "The weather", "The website favicon" ], "answers": [ 1 ], "explanation": "Remote access can expose data across borders even without file copying.", "principle": "International access", "risk": "Unmapped access can bypass transfer controls.", "saferAction": "Record access locations and apply transfer safeguards." }, { "id": 78, "category": "Cross-Border Transfers", "difficulty": "Advanced", "type": "single", "question": "Why is data localization alone not always sufficient?", "options": [ "Local staff never access data", "Foreign remote access and key control may still create exposure", "Local storage deletes data", "Localization removes all security risks" ], "answers": [ 1 ], "explanation": "Data location is only one part of access and control.", "principle": "Effective protection", "risk": "Foreign access can undermine local storage restrictions.", "saferAction": "Control access, keys, administration, and onward transfers." }, { "id": 79, "category": "Privacy by Design", "difficulty": "Beginner", "type": "single", "question": "Privacy by design means privacy is considered:", "options": [ "From the earliest design stages", "Only after launch", "Only after complaints", "Only in marketing" ], "answers": [ 0 ], "explanation": "Early integration prevents costly and risky retrofits.", "principle": "Privacy by design", "risk": "Late reviews may miss architectural problems.", "saferAction": "Include privacy requirements in product planning." }, { "id": 80, "category": "Privacy by Design", "difficulty": "Beginner", "type": "single", "question": "Which default best supports privacy?", "options": [ "Public profile by default", "Minimum sharing by default", "All tracking enabled", "Permanent retention" ], "answers": [ 1 ], "explanation": "Privacy-protective defaults reduce exposure without user effort.", "principle": "Privacy by default", "risk": "Users may never change risky defaults.", "saferAction": "Start with minimal collection, visibility, and retention." }, { "id": 81, "category": "Privacy by Design", "difficulty": "Intermediate", "type": "scenario", "question": "A new app collects contacts automatically on first launch. Better design?", "options": [ "Collect silently", "Ask at the moment needed and explain the purpose", "Upload all contacts permanently", "Share contacts with advertisers" ], "answers": [ 1 ], "explanation": "Just-in-time permission supports informed, contextual choice.", "principle": "Contextual consent", "risk": "Automatic collection surprises users and overcollects.", "saferAction": "Request only necessary contact access when needed." }, { "id": 82, "category": "Privacy by Design", "difficulty": "Intermediate", "type": "multi", "question": "A privacy design review should examine: Select all that apply.", "options": [ "Data flows", "Threats and misuse cases", "Retention rules", "Desk locations" ], "answers": [ 0, 1, 2 ], "explanation": "Design reviews should cover the full data lifecycle and risks.", "principle": "Privacy engineering", "risk": "Hidden flows and missing deletion paths create exposure.", "saferAction": "Map collection, use, sharing, storage, and deletion." }, { "id": 83, "category": "Privacy by Design", "difficulty": "Advanced", "type": "single", "question": "Which architecture best limits breach impact?", "options": [ "One unrestricted database", "Segmentation, tokenization, and scoped services", "Shared production credentials", "Public backups" ], "answers": [ 1 ], "explanation": "Segmentation and tokenization reduce exposure and lateral movement.", "principle": "Defense in depth", "risk": "A single compromise can expose everything.", "saferAction": "Separate sensitive domains and narrowly scope access." }, { "id": 84, "category": "Privacy by Design", "difficulty": "Advanced", "type": "scenario", "question": "A team cannot explain where user data flows after collection. Best next step?", "options": [ "Launch anyway", "Create and validate a data-flow map", "Collect more data", "Disable logging" ], "answers": [ 1 ], "explanation": "A reliable data map supports risk assessment and rights handling.", "principle": "Accountability", "risk": "Unknown flows hide transfers, retention, and access.", "saferAction": "Document systems, vendors, purposes, and deletion paths." }, { "id": 85, "category": "Breaches & Incident Response", "difficulty": "Beginner", "type": "single", "question": "A personal-data breach can involve:", "options": [ "Loss, unauthorized access, alteration, or disclosure", "Only hacking", "Only paper records", "Only public data" ], "answers": [ 0 ], "explanation": "Breaches include confidentiality, integrity, and availability incidents.", "principle": "Breach definition", "risk": "Narrow definitions delay response.", "saferAction": "Train staff to recognize multiple breach types." }, { "id": 86, "category": "Breaches & Incident Response", "difficulty": "Beginner", "type": "scenario", "question": "An employee emails a file to the wrong customer. First action?", "options": [ "Ignore it", "Contain the disclosure and report internally", "Post about it publicly", "Delete all systems" ], "answers": [ 1 ], "explanation": "Rapid containment and escalation support effective response.", "principle": "Incident response", "risk": "Delay can increase further disclosure.", "saferAction": "Recall access where possible and notify the response team." }, { "id": 87, "category": "Breaches & Incident Response", "difficulty": "Intermediate", "type": "multi", "question": "A breach assessment should consider: Select all that apply.", "options": [ "Data sensitivity", "Number of people", "Likely harm", "Office temperature" ], "answers": [ 0, 1, 2 ], "explanation": "Risk depends on the data, scale, context, and consequences.", "principle": "Risk assessment", "risk": "Underestimating harm can delay required action.", "saferAction": "Use a documented breach-risk method." }, { "id": 88, "category": "Breaches & Incident Response", "difficulty": "Intermediate", "type": "truefalse", "question": "Every security incident is automatically a personal-data breach.", "options": [ "True", "False" ], "answers": [ 1 ], "explanation": "A personal-data breach specifically affects personal data.", "principle": "Incident classification", "risk": "Incorrect classification can waste resources or miss duties.", "saferAction": "Determine whether personal data was affected." }, { "id": 89, "category": "Breaches & Incident Response", "difficulty": "Advanced", "type": "single", "question": "Why should an incident log include near misses?", "options": [ "To increase paperwork only", "To reveal patterns and improve controls", "To publish employee names", "To replace backups" ], "answers": [ 1 ], "explanation": "Near misses can expose systemic weaknesses before larger harm occurs.", "principle": "Continuous improvement", "risk": "Repeated warning signs may be ignored.", "saferAction": "Analyze trends and assign corrective actions." }, { "id": 90, "category": "Breaches & Incident Response", "difficulty": "Advanced", "type": "scenario", "question": "A stolen laptop contains strongly encrypted data and no key. What should the team do?", "options": [ "Assume no incident exists", "Assess encryption strength, access, data, and reporting duties", "Publish the key", "Delete unrelated servers" ], "answers": [ 1 ], "explanation": "Encryption can reduce risk but does not eliminate the need for assessment.", "principle": "Breach risk", "risk": "Weak configuration or accessible credentials may still expose data.", "saferAction": "Document evidence and evaluate residual risk promptly." }, { "id": 91, "category": "Governance & Audits", "difficulty": "Beginner", "type": "single", "question": "A data inventory records:", "options": [ "What personal data exists, where, why, and who accesses it", "Only employee names", "Only server prices", "Only website pages" ], "answers": [ 0 ], "explanation": "Inventories support accountability across the data lifecycle.", "principle": "Data governance", "risk": "Unknown data cannot be protected or deleted reliably.", "saferAction": "Maintain and regularly update processing records." }, { "id": 92, "category": "Governance & Audits", "difficulty": "Beginner", "type": "truefalse", "question": "Privacy responsibility belongs only to the legal team.", "options": [ "True", "False" ], "answers": [ 1 ], "explanation": "Engineering, security, operations, HR, and business teams all affect privacy.", "principle": "Shared accountability", "risk": "Siloed ownership leaves operational gaps.", "saferAction": "Assign clear responsibilities across functions." }, { "id": 93, "category": "Governance & Audits", "difficulty": "Intermediate", "type": "multi", "question": "Useful privacy metrics include: Select all that apply.", "options": [ "Rights-request completion time", "Overdue deletions", "Vendor-review status", "Number of decorative icons" ], "answers": [ 0, 1, 2 ], "explanation": "Operational metrics reveal control performance and backlogs.", "principle": "Accountability", "risk": "Unmeasured processes can silently fail.", "saferAction": "Track meaningful risk and compliance indicators." }, { "id": 94, "category": "Governance & Audits", "difficulty": "Intermediate", "type": "scenario", "question": "An audit finds inactive accounts with database access. Best response?", "options": [ "Ignore the finding", "Revoke access, identify root cause, and prevent recurrence", "Create more shared accounts", "Delete audit logs" ], "answers": [ 1 ], "explanation": "Corrective action should address both immediate risk and systemic cause.", "principle": "Remediation", "risk": "Dormant accounts can enable unauthorized access.", "saferAction": "Close accounts and improve identity-lifecycle controls." }, { "id": 95, "category": "Governance & Audits", "difficulty": "Advanced", "type": "single", "question": "What makes a privacy policy operationally effective?", "options": [ "Clear owners, procedures, training, and evidence", "A long document nobody uses", "Marketing language only", "No review schedule" ], "answers": [ 0 ], "explanation": "Policies need implementation mechanisms and accountable owners.", "principle": "Governance", "risk": "Paper-only compliance does not change risky practices.", "saferAction": "Connect policy requirements to controls and evidence." }, { "id": 96, "category": "Governance & Audits", "difficulty": "Advanced", "type": "scenario", "question": "A processing register is two years old. What should happen?", "options": [ "Treat it as permanently accurate", "Validate it against current systems, vendors, and purposes", "Delete it without replacement", "Publish it externally" ], "answers": [ 1 ], "explanation": "Processing records must reflect actual operations.", "principle": "Records of processing", "risk": "Stale records hide new risks and transfers.", "saferAction": "Review inventories on a defined cadence and after changes." }, { "id": 97, "category": "Children's Privacy", "difficulty": "Beginner", "type": "single", "question": "Children’s data often needs:", "options": [ "Enhanced protection and age-appropriate communication", "Less security", "Unlimited profiling", "Public defaults" ], "answers": [ 0 ], "explanation": "Children may be less able to understand long-term privacy consequences.", "principle": "Best interests", "risk": "Complex or manipulative practices can exploit children.", "saferAction": "Use protective defaults and simple explanations." }, { "id": 98, "category": "Children's Privacy", "difficulty": "Beginner", "type": "truefalse", "question": "A privacy notice for children should use clear, age-appropriate language.", "options": [ "True", "False" ], "answers": [ 0 ], "explanation": "Information should be understandable to the intended audience.", "principle": "Transparency", "risk": "Legalistic notices do not support informed choices.", "saferAction": "Use layered, visual, and age-appropriate explanations." }, { "id": 99, "category": "Children's Privacy", "difficulty": "Intermediate", "type": "scenario", "question": "A game enables precise location sharing publicly by default. Best fix?", "options": [ "Keep the default", "Disable public location sharing and require deliberate action", "Share locations with advertisers", "Store locations forever" ], "answers": [ 1 ], "explanation": "Protective defaults reduce risks of stalking and unwanted contact.", "principle": "Privacy by default", "risk": "Public location can create immediate physical risks.", "saferAction": "Use coarse location, private defaults, and clear controls." }, { "id": 100, "category": "Children's Privacy", "difficulty": "Intermediate", "type": "multi", "question": "Which practices better protect young users? Select all that apply.", "options": [ "Minimal profiling", "High-privacy defaults", "Age-appropriate notices", "Dark patterns" ], "answers": [ 0, 1, 2 ], "explanation": "Young users benefit from reduced data use and strong defaults.", "principle": "Best interests", "risk": "Manipulative design can exploit limited understanding.", "saferAction": "Avoid nudges that weaken privacy choices." }, { "id": 101, "category": "Children's Privacy", "difficulty": "Advanced", "type": "single", "question": "Why is age assurance itself privacy-sensitive?", "options": [ "It may require additional identity data", "It always deletes data", "It removes security needs", "It is unrelated to privacy" ], "answers": [ 0 ], "explanation": "Age checks can create new collection and identification risks.", "principle": "Data minimization", "risk": "A protective measure may become an overcollection system.", "saferAction": "Use proportionate, privacy-preserving age assurance." }, { "id": 102, "category": "Children's Privacy", "difficulty": "Advanced", "type": "scenario", "question": "An educational app sells detailed student profiles to advertisers. Main concern?", "options": [ "Battery usage", "Commercial exploitation and incompatible sensitive profiling", "Font choice", "Offline access" ], "answers": [ 1 ], "explanation": "Student data should not be repurposed for intrusive advertising without strong justification.", "principle": "Purpose limitation", "risk": "Profiling can manipulate children and affect opportunities.", "saferAction": "Separate learning functions from advertising and minimize data." }, { "id": 103, "category": "Employee & Workplace", "difficulty": "Beginner", "type": "single", "question": "Employee monitoring should be:", "options": [ "Necessary, proportionate, and transparent", "Secret and unlimited", "Permanent for all purposes", "Based on shared accounts" ], "answers": [ 0 ], "explanation": "Workplace monitoring must balance organizational needs and employee rights.", "principle": "Proportionality", "risk": "Intrusive surveillance can cause unfairness and distrust.", "saferAction": "Define narrow purposes and communicate monitoring clearly." }, { "id": 104, "category": "Employee & Workplace", "difficulty": "Beginner", "type": "truefalse", "question": "Managers should access employee medical records whenever curious.", "options": [ "True", "False" ], "answers": [ 1 ], "explanation": "Health information should be restricted to roles with a legitimate need.", "principle": "Confidentiality", "risk": "Unauthorized access can lead to stigma or discrimination.", "saferAction": "Separate medical records and limit access." }, { "id": 105, "category": "Employee & Workplace", "difficulty": "Intermediate", "type": "scenario", "question": "Keystroke logging is proposed for every remote worker. Best first step?", "options": [ "Deploy secretly", "Assess necessity, alternatives, proportionality, and worker impact", "Publish raw logs", "Keep logs forever" ], "answers": [ 1 ], "explanation": "Highly intrusive monitoring requires a strong, documented justification.", "principle": "Privacy impact assessment", "risk": "Continuous surveillance can be excessive and chilling.", "saferAction": "Use less intrusive performance measures where possible." }, { "id": 106, "category": "Employee & Workplace", "difficulty": "Intermediate", "type": "multi", "question": "Good employee-data controls include: Select all that apply.", "options": [ "Role-based HR access", "Defined retention", "Confidential reporting channels", "Open shared folders" ], "answers": [ 0, 1, 2 ], "explanation": "Workforce data needs controlled access and lifecycle management.", "principle": "Employee privacy", "risk": "Broad sharing can expose pay, health, or disciplinary details.", "saferAction": "Segment records and review permissions." }, { "id": 107, "category": "Employee & Workplace", "difficulty": "Advanced", "type": "single", "question": "Why may employee consent be unreliable?", "options": [ "Employees never read", "Power imbalance can make refusal difficult", "Consent always expires instantly", "Work data is anonymous" ], "answers": [ 1 ], "explanation": "Dependence on employment can undermine freely given choice.", "principle": "Freely given consent", "risk": "Workers may feel pressured to agree.", "saferAction": "Use a more appropriate basis when consent is not genuine." }, { "id": 108, "category": "Employee & Workplace", "difficulty": "Advanced", "type": "scenario", "question": "An HR analytics model uses past promotion decisions. What privacy risk needs review?", "options": [ "Only storage size", "Bias, transparency, necessity, and access to employee profiles", "Screen brightness", "Logo design" ], "answers": [ 1 ], "explanation": "Historical decisions may encode discrimination and affect future opportunities.", "principle": "Fairness and profiling", "risk": "Opaque scoring can unfairly disadvantage workers.", "saferAction": "Test bias, explain use, minimize features, and allow review." }, { "id": 109, "category": "AI & Machine Learning", "difficulty": "Beginner", "type": "single", "question": "Before training a model on personal data, teams should confirm:", "options": [ "Purpose, lawful basis, necessity, and safeguards", "Only model accuracy", "Only GPU speed", "Only brand approval" ], "answers": [ 0 ], "explanation": "Model development does not remove privacy obligations.", "principle": "Responsible AI data use", "risk": "Training can create lasting copies and new inferences.", "saferAction": "Assess data use before experimentation." }, { "id": 110, "category": "AI & Machine Learning", "difficulty": "Beginner", "type": "truefalse", "question": "Removing names always makes an AI training dataset anonymous.", "options": [ "True", "False" ], "answers": [ 1 ], "explanation": "Other attributes and model behaviour may still enable identification.", "principle": "Re-identification", "risk": "Training data may contain unique records or leaked identifiers.", "saferAction": "Evaluate linkage, memorization, and extraction risks." }, { "id": 111, "category": "AI & Machine Learning", "difficulty": "Intermediate", "type": "scenario", "question": "A model predicts health conditions from shopping history. Main privacy issue?", "options": [ "Low screen resolution", "Sensitive inference beyond user expectations", "Slow loading", "Wrong file extension" ], "answers": [ 1 ], "explanation": "Models can create sensitive personal data even when inputs appear ordinary.", "principle": "Inferred data", "risk": "Unexpected inferences can cause discrimination or manipulation.", "saferAction": "Limit inference purposes and provide meaningful transparency." }, { "id": 112, "category": "AI & Machine Learning", "difficulty": "Intermediate", "type": "multi", "question": "Privacy risks in machine learning include: Select all that apply.", "options": [ "Memorization of training examples", "Membership inference", "Model inversion", "Responsive design" ], "answers": [ 0, 1, 2 ], "explanation": "Models may reveal whether someone was included or reconstruct sensitive features.", "principle": "Model privacy", "risk": "Attackers can extract personal information from models.", "saferAction": "Test privacy attacks and reduce memorization." }, { "id": 113, "category": "AI & Machine Learning", "difficulty": "Advanced", "type": "single", "question": "What does differential privacy aim to provide?", "options": [ "A measurable limit on an individual’s influence on outputs", "Perfect model accuracy", "Unlimited data reuse", "A replacement for all security" ], "answers": [ 0 ], "explanation": "Differential privacy controls how much one person can affect released results.", "principle": "Privacy-preserving analytics", "risk": "Weak parameters may provide little practical protection.", "saferAction": "Choose and document an appropriate privacy budget." }, { "id": 114, "category": "AI & Machine Learning", "difficulty": "Advanced", "type": "scenario", "question": "A chatbot logs every conversation indefinitely for training. Best redesign?", "options": [ "Keep all logs forever", "Minimize logs, separate purposes, filter sensitive data, and set retention", "Publish conversations", "Disable deletion requests" ], "answers": [ 1 ], "explanation": "Training reuse requires purpose control, minimization, and lifecycle safeguards.", "principle": "Purpose limitation", "risk": "Conversations may contain highly sensitive or third-party data.", "saferAction": "Offer controls, redact sensitive content, and enforce retention." }, { "id": 115, "category": "Practical Compliance", "difficulty": "Beginner", "type": "single", "question": "What is the safest way to send a sensitive report?", "options": [ "Public link without expiry", "Approved encrypted channel with limited recipients", "Personal social-media message", "Unprotected shared folder" ], "answers": [ 1 ], "explanation": "Secure, controlled channels reduce unauthorized disclosure.", "principle": "Secure sharing", "risk": "Links can be forwarded or indexed.", "saferAction": "Use approved tools, access limits, and expiry." }, { "id": 116, "category": "Practical Compliance", "difficulty": "Beginner", "type": "scenario", "question": "A colleague requests customer data “just in case.” Best response?", "options": [ "Send everything", "Ask for the specific purpose and provide only necessary data", "Share an administrator password", "Post it in group chat" ], "answers": [ 1 ], "explanation": "Access should be justified and minimized.", "principle": "Need-to-know access", "risk": "Vague requests can lead to misuse.", "saferAction": "Verify purpose, authorization, and minimum scope." }, { "id": 117, "category": "Practical Compliance", "difficulty": "Intermediate", "type": "multi", "question": "Before publishing screenshots, check for: Select all that apply.", "options": [ "Names and emails", "Account numbers", "Location details", "Decorative borders" ], "answers": [ 0, 1, 2 ], "explanation": "Screenshots often leak identifiers hidden around the main content.", "principle": "Disclosure prevention", "risk": "Visual data can expose people accidentally.", "saferAction": "Crop, redact, and review screenshots before sharing." }, { "id": 118, "category": "Practical Compliance", "difficulty": "Intermediate", "type": "truefalse", "question": "Using a personal cloud account for work data is acceptable when convenient.", "options": [ "True", "False" ], "answers": [ 1 ], "explanation": "Unapproved services may lack contracts, controls, and organizational oversight.", "principle": "Shadow IT", "risk": "Data can be lost, retained, or accessed unexpectedly.", "saferAction": "Use approved storage and sharing services." }, { "id": 119, "category": "Practical Compliance", "difficulty": "Advanced", "type": "single", "question": "A privacy impact assessment is most useful:", "options": [ "Before high-risk processing is launched", "Only after a breach", "Only for public data", "After all design choices are fixed" ], "answers": [ 0 ], "explanation": "Early assessments help change risky designs before deployment.", "principle": "Risk assessment", "risk": "Late reviews may leave no practical mitigation options.", "saferAction": "Start assessment during planning and update it with changes." }, { "id": 120, "category": "Practical Compliance", "difficulty": "Advanced", "type": "scenario", "question": "A product team wants to copy production data into a test environment. Best option?", "options": [ "Copy everything unchanged", "Use synthetic or minimized masked data with controlled access", "Email the database", "Make the test system public" ], "answers": [ 1 ], "explanation": "Testing rarely needs full identifiable production records.", "principle": "Data minimization", "risk": "Weak test environments can expose real customers.", "saferAction": "Prefer synthetic data and secure any necessary samples." } ]