Community resourceWorksheet
OCR H446 1.3.3 Client server and peer to peer networks
Part 8 of 10 · H446 1.3.3 · Networks
Client-server and peer-to-peer are arrangements of responsibility rather than shapes on a diagram, and that is the distinction H446 1.3.3 rewards. This worksheet asks where services, access control, backup and maintenance are managed in each model, then follows the consequences for cost, scale and resilience.
Students will:
- describe where services, accounts and backups are managed in each model
- explain what each arrangement means for cost, administration and resilience
- recommend a model for a small, short-lived group and justify it from that context
- compare the two models for a large organisation holding confidential shared records
Inside: 5 explanation cells, 1 multiple-choice question, 2 fill-in-the-blanks cells and 2 written answers. 24 marks, about 35 to 45 minutes.
Series: H446 1.3.3 · Networks, part 8 of 10.
Shared by Coding PathwayVerified teacher
- 10 cells
- About 45 minutes
- CC BY-SA 4.0
- Shared 31 Aug 2026
- Updated 3 Sept 2026
Preview
The whole resource, exactly as a class sees it. Answers and marking are held back.
Client-server and peer-to-peer networks
These are responsibility/service models, not required topology names. Ask where services, access control, backup and maintenance are managed, and what follows for cost, scale and resilience.
Two responsibility arrangements
In client-server, clients request data or services from server processes. Central administration can make security, backup, updates and shared data easier to manage, but capable servers/administration cost more and dependence must be managed. Real systems can use several servers, so ‘one server always means one physical single point of failure’ is too absolute.
In peer-to-peer, peers can request and provide resources directly. Setup can be cheap and simple for a small group, but security, backup, versions and availability are distributed and harder to enforce consistently as the group grows.
Worked recommendation
A 90-user design company needs central accounts, controlled access to current project files and verified nightly backups. Client-server is the stronger recommendation: central services fit the named management and consistency constraints. The organisation must fund administration and design resilience for service failure.
The conclusion is not ‘client-server because large’; size matters because it magnifies the stated control and coordination needs.
Which statement best describes peer-to-peer?
- AEvery request must be authorised by one central server
- BIt is another name for client-side web processing
- CIt always uses a bus topology
- DEach peer can request and provide resources, with responsibilities distributed across peers
- requests
- backup
- distributed
- small
- topology
A five-person temporary film crew needs to share non-sensitive draft clips for two days using existing laptops. Recommend a model and explain two benefits plus two drawbacks in this context.
Peer-to-peer is likely, but credit a client-server/cloud-service assumption when made explicit and fully justified.
Students type their answer here.
Apply the model independently
The remaining tasks change the context or reduce the support. Complete them without copying the worked model, then check that each explanation connects a mechanism to its consequence.
A hospital department needs controlled accounts, audited access, reliable backups and shared current records for 140 users. Compare client-server with peer-to-peer and justify a recommendation. Include cost, management and failure/resilience rather than treating either model as perfect.
Use matched criteria and feature → context → consequence chains.
Students type their answer here.
Review your understanding
Before submitting, check that you can explain the main distinction in your own words, apply it in an unfamiliar context and justify each consequence rather than only naming a feature.