---
title: "Quiz: Authentication and Multi-Factor Authentication"
domain: cybersecurity
level: beginner
questions: 10
---

# Quiz: Authentication and Multi-Factor Authentication

## Questions

### 1. In a support portal, a customer enters an email address and a password, and then sees only their own tickets, never other customers' tickets. Which part is **authorization**?
*Objective: 1. Explain the authentication factors and the difference between identification, authentication and authorization.*

- A) Entering the email address
- B) Checking that the password is correct
- C) Limiting the customer to their own tickets
- D) Showing a login page over HTTPS

### 2. A bank asks for a password, a four-digit PIN and the name of the customer's first school before it lets them in. The bank calls this "triple-factor authentication". What is the best description?
*Objective: 1. Explain the authentication factors and the difference between identification, authentication and authorization.*

- A) It is three factors, because three different pieces of information are asked.
- B) It is one factor, because the password, the PIN and the answer are all something you know.
- C) It is two factors, because the PIN is stronger than the password.
- D) It is MFA as soon as the answers are typed on three different screens.

### 3. An auditor reviews a company's password policy: "Exactly 8 characters with upper case, digit and symbol; change every 60 days; pasting is blocked; no other checks." Which change brings it closest to NIST SP 800-63B guidance?
*Objective: 2. Apply current password guidance (NIST SP 800-63B).*

- A) Raise the rotation to every 30 days and require two symbols.
- B) Keep the rules but allow pasting, and add a security question.
- C) Allow only lower-case letters, so people can remember them.
- D) Remove scheduled changes and composition rules, allow long passphrases and pasting, and reject breached or common passwords.

### 4. An employee uses the same password, `Blue-Falcon-2019`, on the company portal and on a small online shop. The shop's database leaks, and a week later someone logs in to the company portal with that password. What happened, and what is the most effective defense?
*Objective: 2. Apply current password guidance (NIST SP 800-63B).*

- A) Credential stuffing; a unique password per site (for example, from a password manager) plus MFA.
- B) Password spraying; a lockout after three failures.
- C) A man-in-the-middle attack; encrypting the company portal.
- D) Brute force; a longer minimum length on the shop.

### 5. A developer must store user passwords for a new application. Which stored record follows good practice?
*Objective: 3. Explain how a server stores passwords safely with a salt and a slow hash function.*

- A) The password encrypted with AES, and the key kept in the application's configuration file
- B) `SHA-256(password)` of each password
- C) A random 16-byte salt per user and the output of Argon2id, scrypt, bcrypt or PBKDF2 for that salt and password
- D) `MD5(password + "mysite")`, with the same extra text for all users

### 6. Fast hashes are good for checking file integrity. Why is a fast hash a **bad** choice for passwords?
*Objective: 3. Explain how a server stores passwords safely with a salt and a slow hash function.*

- A) Fast hashes can be reversed back to the password.
- B) After a database theft, an attacker can guess offline, and a fast hash lets them test billions of guesses per second.
- C) Fast hashes cannot be combined with a salt.
- D) Fast hashes produce output that is too short to store.

### 7. A user's phone clock runs 70 seconds fast. The server accepts the TOTP code for the current 30-second step and one step before and after. What does the user experience?
*Objective: 4. Explain how time-based one-time passwords (TOTP, RFC 6238) are generated and verified.*

- A) The codes are rejected: 70 seconds is more than two steps away, outside the accepted window.
- B) The codes are accepted, because the secret is the same on both sides.
- C) The codes are accepted but only every other time.
- D) The server adjusts the phone's clock automatically.

### 8. Which two inputs does an authenticator app combine to produce a TOTP code?
*Objective: 4. Explain how time-based one-time passwords (TOTP, RFC 6238) are generated and verified.*

- A) The user's password and a counter that rises with each login
- B) A random challenge sent by the server and the user's PIN
- C) The website address and the phone's serial number
- D) The shared secret and the current time step (Unix time divided by 30)

### 9. At 03:10 an employee gets eight approval prompts from the company's authenticator app in a row, and finally taps "Approve" to make them stop. Minutes later, a stranger is inside their mailbox. What is the attack, and what is the best long-term fix?
*Objective: 5. Compare MFA methods (SMS, TOTP, push notifications, FIDO2 security keys and passkeys) by their resistance to phishing.*

- A) SIM swap; switch to SMS codes instead of the app.
- B) Password spraying; force a password change every 30 days.
- C) Push fatigue; require number matching and move to phishing-resistant FIDO2 keys or passkeys.
- D) Cache poisoning; flush the company's DNS resolver.

### 10. Why can a FIDO2 security key or passkey resist a phishing site that a TOTP app can't?
*Objective: 5. Compare MFA methods (SMS, TOTP, push notifications, FIDO2 security keys and passkeys) by their resistance to phishing.*

- A) It generates longer codes that are harder to type quickly.
- B) The key signs a challenge together with the web address the browser sees, so a fake site gets nothing usable.
- C) It sends the code over a separate encrypted network that phishers can't reach.
- D) It makes the user's password unnecessary, so there is nothing to steal.

---

## Answer key

<details>
<summary>Show answers</summary>

| # | Answer | Explanation |
|---|---|---|
| 1 | C | Authorization decides what an authenticated user may do. The email is identification and the password check is authentication. HTTPS protects the connection but is neither. |
| 2 | B | Factors are categories of evidence, not the number of questions. A password, a PIN and a remembered answer are all "something you know", so it is one factor and one phishing page can collect all three. |
| 3 | D | NIST SP 800-63B-4 asks for long passphrases, a blocklist of common and breached passwords, no composition rules, no scheduled rotation and pasting allowed. Options A to C add the practices it advises against (more rules, rotation, security questions) or limit the password further. |
| 4 | A | Credential stuffing reuses leaked pairs on other sites. Unique passwords stop the reuse and MFA covers what remains. Spraying uses one common password on many accounts, which isn't what happened here. |
| 5 | C | A per-user random salt with a slow, purpose-built password hash is the standard. A is reversible by anyone who gets the key, B is fast and unsalted, and D is fast and uses one shared salt, so precomputed tables still help the attacker. |
| 6 | B | Hashes can't be reversed in either case, and salts work with any hash. The issue is speed: offline guessing can't be rate limited, so each guess must be made expensive. |
| 7 | A | 70 seconds is more than two 30-second steps, so even the one-step window doesn't cover it. The user fixes it by turning on automatic time on the phone. |
| 8 | D | TOTP is HMAC of the time step with the shared secret, truncated to digits. A rising counter is HOTP. A server challenge is how WebAuthn works, not TOTP. |
| 9 | C | Repeated prompts until the user taps Approve is push fatigue. Number matching makes blind approval harder, and FIDO2 keys or passkeys remove the prompt the attacker is abusing. SIM swap concerns SMS, not app prompts. |
| 10 | B | The origin is part of what is signed and is supplied by the browser. For a look-alike site there is no credential, and a signature for the fake address is rejected by the real site. A longer code, as in A, could still be relayed. |

</details>
