Q.How is Snooping different from Eavesdropping?
You're viewing a preview — the full solution, concept, methods & PYQ mapping are locked.
Start your 14-day free trial to unlock the full solution →Snooping is a cache coherence protocol where every cache watches the bus for transactions and updates/validates its own copy; Eavesdropping is a security attack where an unauthorised party secretly listens to or copies data in transit.
This is a plain theory question — it asks you to differentiate two terms. The trap is that both involve "listening in" on something, so students often blur them into one idea. But they live in completely different worlds: one is a legitimate hardware mechanism, the other is an illegitimate security threat.
The Core Idea
Snooping is a cache coherence protocol used in multi-processor systems. When several CPUs share memory, each has its own cache. If CPU A updates a variable, CPU B's cached copy of that variable becomes stale. Snooping solves this by making every cache controller watch (snoop on) the bus. When CPU A writes to memory, the bus transaction is visible to all — each cache checks whether it holds the same address and, if so, invalidates or updates its copy. It's a cooperative, hardware-level mechanism designed to keep data consistent.
Eavesdropping is a security attack. An attacker secretly intercepts communication — a network packet, a phone call, a keyboard signal — without the sender or receiver knowing. The goal is to steal information: passwords, credit card numbers, private messages. It's malicious, unauthorised, and happens outside the system's design.
The difference isn't just "who does it" — it's purpose, mechanism, and legitimacy.
Snooping vs Eavesdropping — Point by Point
| Aspect | Snooping (Cache Coherence) | Eavesdropping (Security) |
|---|---|---|
| Domain | Computer architecture / hardware | Network security / cybercrime |
| Purpose | Maintain cache coherence across processors | Steal confidential data |
| Legitimacy | Authorised, designed into the system | Unauthorised, illegal |
| Mechanism | Cache controller monitors the bus for memory transactions | Attacker intercepts packets, signals, or electromagnetic emissions |
| Who does it | Hardware (cache controller) | Malicious software or person |
| Effect | Prevents stale data, ensures consistency | Data breach, loss of privacy |
| Visibility | Transparent to the user, part of normal operation | Hidden, covert |
Why the Confusion Happens
Both terms involve "listening" to something you're not directly part of. In snooping, a cache listens to bus traffic that isn't addressed to it. In eavesdropping, an attacker listens to traffic that isn't meant for them. The surface similarity ends there. …
Unlock everything free for 14 days
- Full step-by-step solutions
- Concept-first explanations
- Methods, shortcuts & mistakes
- PYQ mapping + timed mock tests
Full access for 14 days. No credit card required.