Level 1 exam — Cybersecurity

Exam — fresh questions

12 questions to validate digital hygiene: passwords, two-factor authentication, updates, workstation locking, work/personal separation.
Answer everything, then click Check: your score and explanations will appear.

1.1 · Recall

1. What mostly makes a password strong?

Its length: a passphrase of at least 12-14 characters Changing it every month on displayed principle Complicated symbols on 8 short characters Writing it on a sticky note on the screen

Length beats complexity: 12-14 character minimum, and change on doubt, not on a schedule.

1.1 · Application

2. Karim reuses the same password everywhere. First move?

Change email first to a unique generated password Wait for the next leak to decide what to do Add an exclamation mark to the same password Write all passwords in a shared file

Email is the ROI account: whoever controls it resets all the others — unique and generated first.

1.1 · Arbitration

3. Manager or notebook at the office: what to recommend to Karim?

The “passwords.xlsx” file shared with the team The same simple password everywhere to remember it The encrypted manager: one master, all others unique The sticky note on the screen: visible and handy daily

The manager makes uniqueness painless; at the office, never sticky notes or password files.

1.2 · Recall

4. What should you enable first after passwords?

Sharing the password with a trusted colleague An animated screensaver for visual comfort Two-factor authentication on email first A new official company wallpaper

2FA blocks almost all hijacks by stolen password — email first.

1.2 · Application

5. Karim only has SMS as a second factor. What to do?

Refuse any 2FA until the physical key arrives Disable 2FA because SMS is imperfect Send received codes to a colleague for archiving Enable anyway: SMS beats nothing, app as soon as possible

SMS acceptable as a last resort; the app is recommended, the physical key above.

1.2 · Application

6. Karim loses his phone with the 2FA app. Way out?

The recovery codes saved at setup Create a new account and abandon the old one Guess the code: it follows a simple logic Ask a well-informed stranger for the code

Recovery codes are saved AT SETUP — after the loss, it is too late.

1.3 · Recall

7. Why promptly install security updates?

They add free gadgets and themes They fully replace any existing antivirus They mostly change the workstation wallpaper They close known, actively exploited flaws

Attacks target already-fixed flaws: each postponement leaves a documented door open.

1.3 · Application

8. Karim's workstation has asked for a restart for 15 days. Verdict?

Uninstall antivirus to go faster at the office Restart: 15 postponements = weeks of vulnerability Install a second antivirus to offset the delay Postpone again: restarting only serves comfort

Automatic everywhere + restart when asked; never two antiviruses, never disabled.

1.3 · Arbitration

9. Karim keeps an old end-of-support program. Decision?

Keep it: antivirus offsets missing fixes Report it to IT for replacement: indefensible means replace Copy it to a USB stick to protect it from attacks Disable updates to make it last longer

End of support = no more fixes = indefensible: replace, at IT's pace.

1.4 · Application

10. Karim takes a 2-minute break in open space. Gesture?

Entrust the password to the neighbour to watch Leave open: 2 minutes, no risk among colleagues Switch the screen off without locking, that is enough Lock the session: standing = locked, even 2 minutes

An open session offers email, files and identity to passers-by — traceability, not mistrust.

1.4 · Arbitration

11. A colleague asks for Karim's session “just 2 minutes”. Answer?

Display the password to go faster together Offer the guest session: never your own session Lend without hesitation: among colleagues, trust is enough Refuse bluntly with no useful alternative

Every act under your login is attributed to you: guest session or their session, never yours.

1.5 · Application

12. Karim wants to finish at home and sends the work file to his Gmail. What to do?

Copy to a personal USB stick to bypass IT Share via a personal cloud not monitored by the company Do not transfer: company tools + approved tool asked from IT Send the file to yourself: handy and harmless

Work and personal never mix; real need = approved tool asked from IT, no tinkering.

What's next?

Score ≥ 80%: move on to Level 2 V3 (phishing, attachments, transfer fraud: doubt and verify before acting).
Score < 80%: review the failed sections (passwords 1.1, 2FA 1.2, updates 1.3, locking 1.4, work/personal 1.5), reread the explanations above, then retake the test.