Types of networking between hosts — AQA A-Level Computer Science
Networking between hosts describes how autonomous computing devices interconnect and share resources, primarily using client-server or peer-to-peer (P2P) architectural models. Understanding these paradigms is essential for AQA A-Level Computer Science when evaluating scalability, security, administrative control, and bandwidth utilisation across modern distributed systems.
Types of networking between hosts explained
This statement is an incomplete instruction: the list of items to be explained is absent from the source, so the specific networking types it refers to cannot be stated from the supplied material.
Read the full explanation
The skill being assessed is still clear. Learners must explain how a networking type works and then describe a realistic situation where it would be appropriate. The section concerns types of networking between hosts, which in AQA's specification covers arrangements such as client-server and peer-to-peer networks. A client-server network has dedicated servers providing resources to client computers, suiting larger organisations needing central control and security. A peer-to-peer network has devices sharing resources directly with each other without a dedicated server, suiting small groups such as a home or a small office.
Your focus
- Explain the following and describe situations where they might be used:
Which command word is this?
Set out the causes, reasons, or mechanisms of a concept clearly. Requires connecting phrases (e.g. 'because', 'which leads to', 'therefore') rather than a simple factual statement.
Types of networking between hosts exam tips
Topic Overview
Types of networking between hosts examines the architectural models governing communication, resource sharing, and workload distribution across computer systems. The AQA syllabus focuses primarily on contrasting client-server architectures with peer-to-peer (P2P) models, alongside host roles such as thin and thick clients.
Mastering this topic allows students to critically analyse how software applications, operating systems, and network services interact across distributed environments. It directly underpins subsequent units including network topologies, the TCP/IP stack, web technologies, and distributed databases.
Key Concepts
- →Client-Server Architecture: A centralised structure where client nodes request services or data, and dedicated server hosts manage, process, and respond to those requests.
- →Peer-to-Peer (P2P) Architecture: A decentralised model where every host node maintains equal privilege and capability, acting concurrently as both client and server to share resources directly.
- →Thin-Client Computing: A deployment where endpoint hosts have minimal local hardware resources and rely on a central server to perform computational tasks and storage.
- →Thick-Client Computing: A deployment where endpoint hosts perform the bulk of data processing and application logic locally, using servers mainly for persistent data storage and coordination.
- →Centralised vs Decentralised Administration: Comparison of control over user authentication, access control lists (ACLs), software updates, and backups.
Marking Points
- Defines each networking type accurately, stating how hosts relate to one another.
- Gives a key characteristic of each type, such as central control or direct resource sharing.
- Describes a realistic situation where each type would be used, with a reason linked to its characteristic.
- Explains the advantages or limitations that justify choosing one type over another in a given context.
Examiner Tips
- 💡Structure each answer as definition, key characteristic, then a suitable situation with a reason.
- 💡Use a concrete example such as a small office or a school network to support a situation.
- 💡Check the course materials for the exact networking types that must be explained.
- 💡Always structure comparative questions around specific criteria: hardware cost, administration complexity, scalability, backup management, and single point of failure.
- 💡When explaining peer-to-peer networks, explicitly state that 'peers have equal status and act as both clients and servers' to trigger primary mark scheme points.
- 💡In scenarios asking for recommendations, do not just list features of each model; evaluate the specific trade-offs directly against the scenario constraints (e.g. security compliance vs budget).
Common Mistakes
- Lists features without explaining how the arrangement works; correct by describing how the hosts interact.
- Describes a situation without linking it to a characteristic of the network type; correct by stating why that type suits the context.
- Invents a networking type not covered by the course; correct by checking the specified list of types before answering.
- Believing that the internet itself is exclusively client-server or exclusively peer-to-peer, rather than a hybrid infrastructure hosting both models simultaneously across different application layers.
- Assuming that peer-to-peer networks are inherently illegal or only used for piracy, overlooking legitimate high-performance applications like BitTorrent software distribution, blockchain ledgers, and VoIP protocols.
- Thinking that a 'server' must always refer to a separate physical computer rack, rather than a software process listening for incoming network requests on an assigned port.
Revision Plan
- 1Day 1-2: Draw detailed comparison tables contrasting client-server and peer-to-peer topologies across security, cost, administration, and performance.
- 2Day 3-4: Study thin-client versus thick-client systems, creating real-world use case cards (e.g. airport check-in terminals vs CAD engineering workstations).
- 3Day 5-6: Practise 6-mark scenario evaluation questions, ensuring every point contains a justified link back to the scenario constraints.
- 4Day 7: Review active recall flashcards on key definitions, single points of failure, and P2P protocol mechanisms.
Exam Question Types
- 📋Comparative Explain Questions (2-4 marks): Typically asking students to identify explicit differences between client-server and P2P models.
- 📋Scenario-Based Evaluation Questions (6-9 marks): Requiring students to recommend and justify either client-server, P2P, thin-client, or thick-client models for a specific business or institutional context.
- 📋Technical Short-Answer Questions (1-2 marks): Testing precise terminology such as 'single point of failure' or 'centralised authentication'.
Command Word Expectations (AQA)
Set out the causes, reasons, or mechanisms of a concept clearly. Requires connecting phrases (e.g. 'because', 'which leads to', 'therefore') rather than a simple factual statement.
Review information from both perspectives (e.g. benefits vs drawbacks of client-server vs P2P), make judgements based on the provided scenario, and reach a reasoned conclusion supported by evidence.
Identify both similarities and differences between two network models systematically, using explicit comparative terminology.
How Students Lose Marks (Examiner Pitfalls)
Step-by-Step Worked Solutions
Question: A small media production startup with 6 employees wants to share large 4K video project files locally without purchasing expensive server infrastructure. However, their lead editor wants centralised user access logs for client confidentiality compliance. Evaluate whether a peer-to-peer network or a client-server network is more suitable for this company. [6 marks]
- 1.Step 1: Analyse the context and requirements. Requirements include handling large 4K video files, minimal infrastructure cost (low budget), and centralised access logging for confidentiality compliance.
- 2.Step 2: Evaluate Peer-to-Peer (P2P) in this context. P2P has low setup costs and does not require a dedicated server; high file transfer speeds can occur directly between host workstations. However, auditing access logs centrally is technically infeasible because each host operates autonomously without a unified logging mechanism.
- 3.Step 3: Evaluate Client-Server in this context. A dedicated fileserver or Network Attached Storage (NAS) server enables centralised authentication, granular permissions, and automated audit logs required for client confidentiality. It also avoids performance bottlenecks on individual editing workstations. The drawback is higher initial hardware and setup cost.
- 4.Step 4: Formulate a balanced conclusion. Although P2P satisfies the low-cost requirement, it fundamentally fails the regulatory compliance requirement for centralised access logs. Client-server is therefore the necessary architecture.
Question: Explain two operational differences between a thin-client and a thick-client implementation in a client-server network. [4 marks]
- 1.Step 1: Define the processing distribution between thin and thick clients. In a thin-client model, application processing is executed predominantly on the central server, with the client acting primarily as an input/output terminal. In a thick-client model, application processing is handled locally by the client machine's own CPU/RAM.
- 2.Step 2: Contrast hardware specifications and storage. Thin clients require minimal local storage, lower-spec processors, and lower maintenance since operating environments run on the server. Thick clients require high-specification local hardware, dedicated storage, and locally installed software.
- 3.Step 3: State the network bandwidth implications. Thin clients require continuous, low-latency network connectivity to transmit keystrokes, mouse events, and display updates. Thick clients can operate offline or with intermittent connectivity, uploading and downloading only data files as required.