500-560 · Question #109
What is one typical need of a small branch?
The correct answer is A. multiple network services integrated into a single device. Small branches operate with tight budgets and limited physical space, so they rely on a single, multi-function device that bundles routing, switching, wireless, and security into one unit - this minimizes cost, hardware footprint, and management complexity. This is the defining c
Question
What is one typical need of a small branch?
Options
- Amultiple network services integrated into a single device
- Bcomprehensive subscription-based services
- Cmultiple devices for optimal flexibility
- Dability for users to access the majority of resources at off-site data storage
How the community answered
(31 responses)- A94% (29)
- B3% (1)
- D3% (1)
Explanation
Small branches operate with tight budgets and limited physical space, so they rely on a single, multi-function device that bundles routing, switching, wireless, and security into one unit - this minimizes cost, hardware footprint, and management complexity. This is the defining characteristic of small branch network design, making A correct.
B is wrong because "comprehensive subscription-based services" implies enterprise-scale managed services - far beyond a small branch's typical scope or budget. C is wrong because multiple devices bring higher cost and complexity, which is the opposite of what a small branch needs - that's an enterprise or large campus requirement. D is wrong because while small branches do connect to central/off-site resources, relying on the majority of resources being off-site describes a WAN dependency, not the fundamental equipment need that defines a small branch design.
Memory tip: Think "small branch = small budget + small space = one device does all." The integrated device trades flexibility for simplicity - one box, one bill, one management interface.
Topics
Community Discussion
No community discussion yet for this question.