ASSIGNMENT 5 · CHAPTER 14
Keep one critical service running
Use the familiar decision-and-evidence sequence. This chapter focuses on critical service → degraded mode → recovery check. Make the initial decision before seeing the new evidence.
- Warm-up
- FIT → RECOVER → BOUND → ACT + EVIDENCE
- Commit Part A
- STRESS → REFIT
- AI declaration + human review
- Export and submit in LMS
1 · WARM-UP · 5 MINUTES · NOT GRADED
A backup server starts successfully. Is the essential service necessarily recovered?
Show / hide warm-up answer
No. Check data freshness, dependencies, user access and the ability to deliver the required service. Process uptime alone is not a service-level recovery result.
No written warm-up response is required.
Lecture guide
X02, X04, D14, X06 and B01; original slides 6–17 and 28–61.
FIT identifies the relevant problem. RECOVER builds this chapter’s artifact. BOUND states the limits. ACT + EVIDENCE records the action, owner and verification. STRESS then tests your reasoning before REFIT.
READ BEFORE ANSWERING
How your work is assessed · 5 points
| Criterion | Scoring |
|---|---|
| FIT · 1 point | 1: Defines the chapter-specific problem accurately, distinguishes facts from assumptions and connects it to the proposed action. 0.75: Sound reasoning with one minor omission. 0.5: Partly correct, with a consequential gap. 0: Missing, materially incorrect or based on invented evidence. |
| RECOVER · 1 point | 1: A coherent response across the four resilience activities, including usable degraded service, reconciliation and a testable recovery check. 0.75: Sound reasoning with one minor omission. 0.5: Partly correct, with a consequential gap. 0: Missing, materially incorrect or based on invented evidence. |
| BOUND · 1 point | 1: States relevant operating assumptions, scope and an observable trigger to reconsider the claim. 0.75: Sound reasoning with one minor omission. 0.5: Partly correct, with a consequential gap. 0: Missing, materially incorrect or based on invented evidence. |
| ACT + EVIDENCE · 1 point | 1: Gives a feasible bounded action, named responsibility and inspectable evidence, while distinguishing completed from proposed verification. 0.75: Sound reasoning with one minor omission. 0.5: Partly correct, with a consequential gap. 0: Missing, materially incorrect or based on invented evidence. |
| REFIT · 1 point | 1: Explains how the new evidence affects the initial claim and justifies RETAIN, REVISE or REPLACE with a coherent final record. 0.75: Sound reasoning with one minor omission. 0.5: Partly correct, with a consequential gap. 0: Missing, materially incorrect or based on invented evidence. |
Five points use the same familiar structure. The chapter artifact changes; the LMS determines how assignment points contribute to the course grade.
Learning-outcome alignment
This task supports supplied syllabus CLO 6. It practises disciplinary knowledge, engineering skills and accountable decisions. It is course-written practice, not an official national readiness assessment or an approved item-weight mapping.
Before you start
Use Save draft while working and Download draft / backup before leaving a shared device. Part A becomes read-only only after you confirm commitment. You can continue editing Part B afterward.
The new evidence opens automatically after you commit Part A. No unlock code is required. Your initial reasoning stays saved and read-only. The sequence is designed to preserve your first judgment; it is not a secure examination system.
Identity
Loaded from the entry page. Drafts are separated by Student ID in this browser.
Submission details
Check the current deadline and submission instructions in the LMS.
2 · PART A · 20 MINUTES
Assessed scenario · fictional teaching case
A fictional campus transport desk must retain access to the day’s pickup list when its central scheduling server is unavailable. A local copy is refreshed at 06:00. Authorized staff can read it on a desk device. Changes after 06:00 normally remain on the central server until the next refresh. The brief includes a successful restart log for a backup server, but no full service rehearsal. Staff can record changes on a controlled paper form during an outage. You recommend whether this fallback is ready for a limited trial.
Aim for 300–450 focused words overall. Use a small table or clear notation for the chapter artifact. No code or external experiment is required. Cite at least one relevant Chapter 14 unit/title or source page supporting your artifact and mechanism.
A1 · FIT · 1 POINT
Name the essential service and distinguish it from full normal functionality. Identify the users and dependencies that matter during failure.
A2 · RECOVER · 1 POINT
Describe recognition, resistance, recovery and reinstatement for one outage. Include how staff check data freshness and reconcile paper changes. Mark untested steps as proposed.
A3 · BOUND · 1 POINT
State the allowed operating scope and the staleness or confidentiality condition that makes the fallback unacceptable. Any new threshold must be labelled proposed.
A4 · ACT + EVIDENCE · 1 POINT
Choose trial, restricted trial or hold. Give the immediate action, owner and one rehearsal that would test the service rather than only the server.
Name the relevant test/log/audit, the conditions it must cover, who checks it, and what evidence is still missing. Do not describe requested evidence as if it already exists.
Commit is not LMS submission. Confirmation freezes FIT, RECOVER, BOUND, ACT and EVIDENCE before the new information appears.