Chapter 8 · Reading 3 of 5
Reviewing a proposed architecture change
Security+ SY0-801 · Objectives 3.1, 3.2
The college wants to send appointment reminders ten minutes after a booking is confirmed. The design team proposes putting work on a queue so that a slow mail service cannot prevent a student from making a reservation. The change makes sense to the registrar. What new security and recovery questions does it introduce?
Draw the work that happens after the student leaves
The student talks to the booking application. The application places a job on a queue. A worker reads the job and asks a mail provider to deliver it. Draw each identity and data store on the diagram. Decide whether the queue needs a full student record, a message address or just a reference the worker can resolve when authorized. Less information in the queue can reduce disclosure, but the worker may then depend on another service to retrieve what it needs.
The worker should have permission to read the relevant jobs and request the intended delivery. It has no obvious reason to change appointment ownership. Decide who can place work on the queue, how the worker recognizes an authorized request and where an unexpected destination is rejected. Ask who will receive an alert if the worker stops reading while new bookings continue to arrive.
A queue has a capacity as well as a purpose
During an exercise imagine the mail worker can send twenty approved reminders a minute. Fifty bookings arrive each minute for ten minutes. If every booking needs one reminder and the worker continues at that rate, three hundred reminders accumulate. The queue preserved work, but the oldest messages will take time to drain. An alarm based only on whether the worker is running would miss the delay entirely.
Ask the advising team how late a reminder may arrive and still help a student. Monitor the age of the oldest eligible job as well as the number of queued jobs. A queue full of recent notices and a short queue containing one week-old undeliverable notice need different responses. Define who reviews failed deliveries and how that reviewer can work without exposing all student addresses.
Trace a failure halfway through
Suppose the provider accepts a reminder but the worker loses contact before marking the job complete. The queue can offer the same work again. Have the workflow reconcile a stable job identifier with the delivery receipt before retrying. Consider the opposite failure too: a worker might record success before any delivery occurred. An audit trail should distinguish requested, accepted and completed actions.
Follow the privacy consequences of a retry. If an appointment has been canceled or its contact changed, an old queued message may now go to an inappropriate destination. Decide how the worker checks current authorization and which team can suspend delivery while leaving the booking service available. Set retention for failed jobs and limit who can inspect them, because failures can contain the very records you sought to protect.
A design review is successful when it leaves a testable set of expectations. Demonstrate that booking still works when mail is unavailable, that a duplicate job is reconciled and that a canceled appointment produces no unauthorized reminder. Identify the owner for each observation. You now have an architectural drawing that predicts behavior during a failure, which makes it much easier to see dependencies shared by apparently independent systems.
Inspect the three records, then use the evidence to answer the question.
1. Worker
Worker reads reminder job J42 from the queue.
2. Queue
Mail service accepts message J42.
3. Delivery receipt
Worker stops before it acknowledges J42 to the queue.
Apply the reading
What must the worker recheck before sending a delayed reminder?
Compare your reasoning
Reconcile prior delivery, current appointment state, approved recipient and the authority to send.