156-561 · Question #126
What is a Spoke function?
The correct answer is A. To provide isolated environments to deploy applications and services. In a hub-and-spoke network architecture (common in cloud platforms like Azure Virtual WAN), a Spoke is an isolated virtual network environment that connects back to a central Hub, making A correct - its primary purpose is to provide isolated environments where applications and…
Question
What is a Spoke function?
Options
- ATo provide isolated environments to deploy applications and services
- BTo provide a separate subnet for applications
- CTo provide a Workload with availability
- DTo provide a Workload with scalability
How the community answered
(36 responses)- A92% (33)
- C6% (2)
- D3% (1)
Explanation
In a hub-and-spoke network architecture (common in cloud platforms like Azure Virtual WAN), a Spoke is an isolated virtual network environment that connects back to a central Hub, making A correct - its primary purpose is to provide isolated environments where applications and services are deployed.
Why the distractors are wrong:
- B is wrong because a Spoke is a full virtual network (VNet/VPC), not merely a subnet - subnets exist within a network, not as a separate topology unit.
- C is wrong because availability (redundancy/uptime) is addressed through replication, load balancers, and availability zones - not by the Spoke itself.
- D is wrong because scalability relates to handling increased load (auto-scaling, etc.) - again, a function of the workload's configuration, not the Spoke topology.
Memory tip: Picture a bicycle wheel - the Hub sits at the center managing shared services (firewalls, DNS, gateways), and each Spoke radiates outward as its own isolated environment. "Spokes = Separate, isolated Spaces."
Topics
Community Discussion
7
Lena V.Jun 21, 2026Answer is A. A Spoke provides isolated environments where you deploy your applications and services, which is core to the hub-and-spoke network model the exam tests you on, so do not confuse it with subnetting (B) or the availability/scalability concepts in C and D, those belong to different constructs entirely.
Viktor S.Jun 22, 2026Lena's got the right flag planted but "isolated environments" is doing too much lifting here, the real point is that a Spoke is a VNet peered back to a Hub VNet so traffic flows through a shared set of centralized services like firewalls and gateways, which is why B, C, and D fall apart on the architecture level, not just the vocabulary level.
Wesley A.Jun 18, 2026The subnet answer in B is the trap that got me the first time, because spokes do involve network separation, but a subnet is just a Layer 3 concept and nowhere near what a Spoke actually does in this architecture. A is the move, a Spoke provides isolated environments to deploy applications and services, which is exactly what the Hub and Spoke model is designed around.
Luis F.Jun 21, 2026Wesley nailed it, and I'd just add that the isolation a Spoke gives you also makes it way easier to apply granular RBAC and network policies per team or workload without that bleeding into the hub or other spokes.
Luis F.Jun 26, 2026So this one tripped me up at first because option C sounds really close to what a spoke does in practice, but availability is more of a benefit you get from your overall hub-and-spoke topology, not the actual function of a spoke itself. The real job of a spoke is A, giving you that isolated environment where you can drop your apps and services without them stepping on each other or on the hub. Think of it like separate rooms in a house, the hub is the hallway everything connects through, and each spoke is its own room with its own stuff. Option B is a red herring too since a spoke is a VNet (or equivalent network segment depending on your cloud), not just a subnet inside one.
Viktor S.Jun 26, 2026A is right, Spokes are isolated environments for deploying workloads, that is the whole point of hub-and-spoke topology, the hub handles shared services and the Spokes keep your apps separated from each other.
Luis F.Jun 29, 2026Viktor nailed the core idea, though I'd add that spokes also isolate network traffic through VNet peering back to the hub, so lateral movement between workloads is blocked by design, not just by convention.