OpenCyber AcademyLesson map
Lesson 09. Map, example, EX055.
flowchart TD
A["Tuple: admin, Rosa and Mia, no MFA, shared"] --> B["Week four adds a staff role"]
B --> C{"Does the role become a new tuple?"}
C -->|No| D["Leave Rosa, Mia on the printed row"]
C -->|Yes| E["No staff name is in the list"]
Admin rights and a view-only role are a design. The print still shows one shared admin row.
Logical drawing
printed row
online shop, admin, Rosa and Mia, no MFA, shared
week-four design
staff may view and pack
staff may not change prices or payments
only Rosa and Mia keep admin
not printed
any other person's name
Learning outcomes
After this chapter, you should be able to:
- Read the shop-admin tuple as printed.
- Keep the staff role in the narrative.
- Refuse to add a name to the row.
9.1 The tuple names two people. The role does not add a third.
The account row says the online shop admin is used by Rosa and Mia, the second-step flag is false, and the shared flag is true. The print says no MFA: online shop (admin) - shared. That row is why a takeover could change prices or redirect payments, which is the harm chapter 1 names, and why chapter 3 ranks this gap second, after the orders mailbox. Week four describes a staff role that can view and pack orders and cannot change prices or payment settings, with each staff member given a personal login. Only Rosa and Mia keep admin, both with a second step in that narrative. The account list does not gain a row for the staff role, and it does not gain a personal name. Six staff remain an unnamed group. Writing another name into "Rosa, Mia" would invent a user the synthetic list does not contain. The checklist item "MFA on online shop admin" belongs to the other script's after set. It does not delete this no MFA line.
9.2 Worked example
Quote the users who are written. Stop before the users who are only described as "staff".
Lesson table; scroll horizontally to read all columns →
| Statement | In the account tuple? | Decision |
|---|---|---|
| Users are Rosa and Mia | Yes | May stay |
| The row is shared and has no second step | Yes, on the print | May stay |
| A staff role views and packs, not prices | Chapter 4 prose | May stay as prose |
| A named colleague was added to the tuple | No name | Refuse |
Synthetic case. The admin row is a synthetic tuple. No shop price is changed.
Errors and limits
A narrower role is a good design and still not a new laboratory line. Unnamed staff stay unnamed.
Apply
- EX055 — Who is on the admin row? Week four creates a view-and-pack role. The account print still has one online-shop line. Who does that line name, and what must you not add?
Show marking criteria
Rubric: 3 = the printed users stay Rosa and Mia; the row stays no-MFA and shared; the staff role stays prose; no new name is added;; 2 = Rosa and Mia stay the printed users;; 1 = the role only;; 0 = none.