A () network is suitable for an enterprise with no more than 20,000 users that does not have branches or has branches that do not require bcal regeneration.

Question

Options

• ASingle -node
• BCentralized call management
• CDistributed call management (peer-to-peer mode)
• DDistributed call management (aggregation mode)

• A
  82% (27)
• B
  6% (2)
• C
  9% (3)
• D
  3% (1)

Explanation

Single-node is correct because it is designed for enterprises with up to 20,000 users that operate from a single location or have branches that can rely entirely on the central site for call processing - no local call regeneration at branch sites is needed. Centralized call management (B) is a broader architectural concept, not a specific deployment topology matching those exact constraints. Distributed call management in peer-to-peer mode (C) is used when branches need to independently process calls and maintain survivability without relying on a central node, which is the opposite of the stated requirement. Distributed call management in aggregation mode (D) is suited for larger or more complex deployments where multiple nodes aggregate capacity across sites.

Memory tip: Think "single = simple" - one node handles everything when the scale is modest (≤20,000 users) and branches don't need to generate their own calls locally. Once branches need autonomy, you move to distributed.

No community discussion yet for this question.