OpenCyber Academy
Rapid course · Lesson 13 · English
Course code: OCA-007Lesson 13: OCA-007-A013

Questions before signing are not a new lab row

Open, free learning for anyone who wants to protect people and technology. No account is required to read this text or its worked answers.

Lesson map

Lesson 13. Map, example, EX059.

flowchart TD
  A["Budgeting app would add a supplier"] --> B["Board asks security questions"]
  B --> C{"Is there a signature or a new print row?"}
  C -->|No| D["Keep the questions and the old print"]
  C -->|Yes| E["The file does not show either"]

The map shaped a decision before money was spent. It did not record a signature.

Logical drawing

overview, used before a purchase
    new supplier would hold transaction data
    another dependency on the identity provider
board
    asks vendor security questions before signing
not in the file
    a signature
    a vendor name
    a new services-dictionary row

Learning outcomes

After this chapter, you should be able to:

  1. Keep the budgeting app as an unsigned proposal.
  2. Keep the board's questions as the recorded action.
  3. Leave the dependency print unchanged.

13.1 The board asked. The file does not show a signature.

When the board considers a budgeting app, the architecture overview shows a new supplier holding transaction data and another dependency on the identity provider. The board asks the vendor security questions before signing. A classmate treats the questions as a signature, names a vendor, and adds the app to the dependency dictionary so identity moves from 6 to 7. The book records the questions and does not record a signature or a name. Leah does not insert a row. She does not edit lab_deps.py. The older print stays the count already run.

13.2 Worked example

Lesson table; scroll horizontally to read all columns →

Step In the file Decision
The app would add a supplier and an identity dependency The overview discussion May stay
Questions were asked before signing The board's action May stay
"They signed." No signature Refuse
"Add the app and print identity 7." No new run Refuse

Synthetic case. No vendor is named. No contract is signed in this lesson.

Errors and limits

Questions before signing do not answer themselves. The book does not record what the vendor replied.

Apply

Worked answers

EX059. Questions before signing stay the recorded action. A signature is not in the file. Do not name a vendor. Do not add a row. Do not edit the script.