Given a company's planned implementation of BlackBerry Enterprise Server software version 5.0, how can they ensure that the BlackBerry Enterprise Server instances have stable connectivity to the…

Question

Options

• ACreate a BlackBerry Router pool
• BCreate a BlackBerry MDS Connection pool
• CCreate a BlackBerry Administration Service pool
• DCreate a BlackBerry Collaboration Service pool
• ECreate a BlackBerry Load Balancing pool

• A
  70% (33)
• B
  2% (1)
• C
  15% (7)
• D
  9% (4)
• E
  4% (2)

Explanation

Option A is correct because the BlackBerry Router is the specific component that manages outbound connections from the BlackBerry Enterprise Server to the BlackBerry Infrastructure (RIM's NOC). Creating a BlackBerry Router pool groups multiple Router instances together, providing failover and redundancy so that if one Router loses its connection to the BlackBerry Infrastructure, another picks up seamlessly - ensuring stable, uninterrupted connectivity.

Why the distractors are wrong:

• B (MDS Connection pool): The MDS Connection Service handles connections to internal corporate web/application servers, not the BlackBerry Infrastructure.
• C (Administration Service pool): The Administration Service is the web-based management console for administering BES - it has no role in infrastructure connectivity.
• D (Collaboration Service pool): The Collaboration Service manages real-time features like instant messaging and presence; it doesn't touch the BlackBerry Infrastructure link.
• E (Load Balancing pool): There is no standalone "Load Balancing pool" component in BES 5.0 - load balancing for infrastructure connections is achieved through the Router pool, making this a trap answer.

Memory tip: Think "Router = Road to RIM." The Router is the outbound gateway to BlackBerry's network, so pooling Routers = stable roads to the infrastructure. Everything else (MDS, Admin, Collaboration) faces inward toward your corporate network.

No community discussion yet for this question.