400-007 practice question 25 of 35

As network designer, which option is your main concern with regards to virtualizing multiple network zones into a single hardware device?

Full set: 397 questions
Answer options
A: Fate sharing Correct answer
B: CPU resource allocation
C: Congestion control
D: Security
E: Bandwidth allocation
Correct Answer:
A. Fate sharing
Explanation

Fate sharing is the primary architectural concern when consolidating multiple independent network zones onto a single hardware device. This design principle refers to a situation where multiple components are reliant on a single, common component for their operation. In this scenario, the physical hardware is the common component. A failure of this single device (e.g., power supply, CPU, or critical software crash) will cause all virtualized network zones to fail simultaneously. This creates a significant single point of failure (SPOF), which fundamentally undermines the resilience and availability that separate physical zones are meant to provide.

Why Incorrect

B. CPU resource allocation: This is a valid operational concern related to performance, but it can be managed with resource pools and scheduling, not a fundamental architectural risk like a total outage.
C. Congestion control: This is a traffic management and performance issue within the device, which is a secondary concern compared to the complete failure of all zones.
D. Security: While security is critical, modern hypervisors provide strong logical isolation between virtual instances. The more immediate and certain architectural risk is the total system unavailability from a single hardware failure.
E. Bandwidth allocation: Similar to CPU allocation, this is a manageable resource contention issue, not the primary concern of a catastrophic, system-wide failure.

References

1. White

R.

& Donohue

D. (2014). The Art of Network Architecture: Business-Driven Design. Cisco Press.

Reference: Chapter 6

"Resiliency

" Section "Fate Sharing." The chapter explains

"Fate sharing simply means that two or more components are reliant on the same component or components to operate correctly... Placing multiple logical systems on a single physical piece of hardware is another common form of fate sharing." This directly supports that fate sharing is the core design principle at risk in the question's scenario.

2. Al-shawi

M. (2016). CCDE Study Guide. Cisco Press.

Reference: Chapter 2

"The Design Lifecycle

" Section "Analyzing the Design Requirements." The text emphasizes that a key design goal is availability

which is "often achieved by providing redundancy to eliminate single points of failure (SPOFs)." Virtualizing multiple zones on a single device creates a classic SPOF

the direct result of fate sharing.

3. Cisco. (2021). Campus Network for High Availability Design Guide. Cisco Design Zone.

Reference: Section "Failure Domain." This guide discusses the importance of limiting the "failure domain" or "blast radius" of any single component failure. The principle is to "avoid fate sharing where possible." Consolidating multiple security zones onto one device maximizes the failure domain

making it a primary design anti-pattern from a high-availability perspective.

Scroll to Top