S6 ICT: system maintenance and documentation (error rework)
- 2026-11-20
S6 ICT: system maintenance and documentation (error rework)
Error rework only: ten common confusions corrected item by item, including RTO read as RPO and 1.5.0 answered for 1.4.9.
Error rework: the ten commonest confusions This paper does one thing: correct the ideas that keep going wrong. Maintenance is not just bug fixing, since corrective work is 55 percent; perfective is not corrective; backup is not archiving; RTO controls time while RPO controls data; 1.4.9 is followed by 1.4.10 because versions are not decimals; an incremental restores only on top of the last full; heavy commenting is not documentation; a smaller MTTR raises availability; 99.9 percent is 8.76 hours a year, not 87.6; and testing never stops in maintenance, regression most of all.
01 Paper details (check answers afterwards)
| Item | Detail |
|---|---|
| Questions | 10 |
| Suggested time | 25 |
| Difficulty mix | Foundation 4 · Intermediate 2 · Challenge 2 · Error redo 2 |
| Chapter | Chapter: S6 ICT: System maintenance and documentation |
| Level | Error rework (10 items) |
02 Questions (10 items)
- FoundationDoes system maintenance mean fixing bugs?
- FoundationIs perfective maintenance the same as corrective maintenance?
- FoundationAre backup and archiving the same thing?
- FoundationCan RTO and RPO be used interchangeably?
- IntermediateAfter 1.4.9, is the next bug-fix version 1.5.0?
- IntermediateCan an incremental backup be restored on its own?
- ChallengeDoes heavy code commenting mean documentation is complete?
- ChallengeDoes a larger MTTR raise availability?
- Error redoAt 99.9 percent availability, is yearly downtime 87.6 hours?
- Error redoOnce a system is in maintenance, is testing no longer needed?
03 Answers and one-line notes
| # | Answer | One-line note |
|---|---|---|
| 1 | No. Corrective work is about 55 percent; adaptive, perfective and preventive work make up the other 45 percent. | A team that only fixes bugs is eventually dragged down by environment change and efficiency problems. |
| 2 | No. Corrective maintenance repairs faults; perfective maintenance adds features or improves efficiency in a working system. | Their purposes are opposite: one rescues, the other adds value. |
| 3 | No. Backup serves restore: short term, overwritable, drilled. Archiving serves retention and compliance: long term, read only, kept for a fixed period. | Using backups as an archive means the evidence is overwritten when you need it. |
| 4 | No. RTO caps the time to restore service; RPO caps acceptable data loss. | Confusing them produces a four-hour recovery that still loses half a day of data. |
| 5 | No, it is 1.4.10. Only a feature change bumps the middle digit to 1.5.0. | Version numbers are not decimals; 1.4.10 follows 1.4.9. |
| 6 | No. Restore the last full backup first, then apply each incremental in order. | A restore drill must test the whole chain, not just the full backup. |
| 7 | No. Comments explain code detail; documentation also needs architecture diagrams, a data dictionary, install and restore steps, and an operator manual. | Comments serve the coder; documents serve the operator and maintainer. |
| 8 | No, the opposite. Availability equals MTBF over MTBF plus MTTR, so a smaller MTTR gives higher availability. | Per point of availability, cutting MTTR is usually cheaper than stretching MTBF. |
| 9 | No. 8,760 times 0.1 percent is 8.76 hours; 87.6 hours corresponds to 99 percent. | One misplaced decimal shifts the answer by a factor of ten. |
| 10 | No. Every change needs unit, integration and regression testing, and major changes still need user acceptance. | Most maintenance incidents come from fixing one place and breaking another. |
04 What to do after marking
- After marking, redo only the wrong items and write down which step went wrong (formula, unit, or misread number).
- Repeat the same item two days later; move to the next paper only when both attempts are correct.
- Parents only need the answer and note columns; there is no need to explain every item.
Want the four maintenance types, availability and MTTR conversions, plus RTO, RPO, backup maths and documentation coverage all settled? Book a TutorZone tutor and work through every figure in twenty-five minutes.Tutor Registration →
Questions and answers are written originally by the TutorZone team and are not taken from any school, publisher or examination authority paper. Every value is checked by computer.



