Paper 4: Common mistakes corrected
- 2026-11-21
Paper 4: Common mistakes corrected
Chapter practice with ten items, answers and a one-line note for each, about 25 minutes.
Paper 4 Ten items on this chapter with answers for immediate marking.
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: Cloud computing and virtualisation |
| Level | Retry |
02 Questions (10 items)
- FoundationA student says all cloud must be public and internet-facing. What is wrong?
- FoundationA student says virtual machines need no operating system. What is wrong?
- FoundationA student says containers bundle a full OS and are heavier than VMs. What is wrong?
- FoundationA student says 99.9% availability means no downtime. What is wrong?
- IntermediateA student says SaaS users must patch the underlying servers. What is wrong?
- IntermediateA student says pay-as-you-go is always cheaper than owning hardware. What is wrong?
- ChallengeA student says auto-scaling can add unlimited machines. What is wrong?
- ChallengeA student says the provider is fully responsible for data security in the cloud. What is wrong?
- Error redoA student says each VM performs exactly like a physical server. What is wrong?
- Error redoA student says backups in the same region as production are enough. What is wrong?
03 Answers and one-line notes
| # | Answer | One-line note |
|---|---|---|
| 1 | Private and hybrid clouds are still cloud computing and can run on internal networks. | Pooling and self-service define cloud, not public exposure. |
| 2 | Each VM runs its own guest OS that must be installed and patched. | A VM is a full machine abstraction, guest OS included. |
| 3 | Containers share the host kernel and ship only the app and its dependencies, so they are lighter. | Claiming a full OS inside makes a container sound like a VM. |
| 4 | 99.9% still allows 8.76 hours a year, so redundancy is still required. | Availability is a ratio, not a promise of zero failure. |
| 5 | The provider manages the platform; users only manage accounts and data. | SaaS leaves platform and infrastructure to the vendor. |
| 6 | For steady high load, owned or reserved capacity can be cheaper; compare real usage. | Pay-as-you-go buys flexibility, not the lowest price in every case. |
| 7 | Quotas, budget and database bottlenecks all cap scaling. | Check quotas and downstream capacity before relying on scale-out. |
| 8 | Under the shared responsibility model the customer still owns accounts, permissions and data. | Most breaches come from customer misconfiguration such as public buckets. |
| 9 | Virtualisation overhead and contention with neighbour VMs reduce performance. | Overcommit and noisy neighbours mean below-bare-metal throughput. |
| 10 | A regional failure takes both down, so backups belong in another region. | Backups must survive region-level incidents to count. |
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 whole chapter? See all four difficulty papers on the chapter page.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.



