Nextair Corporation wants to be able to efficiently manage the BlackBerry solution at all times. How can this be accomplished if a BlackBerry Enterprise Server is installed in two different cities?…

Question

Options

• ASet up one of the BlackBerry Enterprise Server instances as a standby instance
• BCreate a pool of BlackBerry Administration Service instances
• CEnable automatic connections failover
• DSetup BlackBerry MDS Integration Service in a round robin configuration

• A
  6% (3)
• B
  80% (40)
• C
  10% (5)
• D
  4% (2)

Explanation

Creating a pool of BlackBerry Administration Service (BAS) instances allows administrators to manage all BlackBerry Enterprise Servers across both cities from a single, unified console - any BAS instance in the pool can administer any BES, making management centralized and efficient regardless of geographic location.

Why the distractors are wrong:

• A (Standby instance): A standby BES handles failover for user continuity, not centralized management - it doesn't solve the multi-city administration problem.
• C (Automatic connection failover): Failover ensures service continuity if a BES goes down, but it's a redundancy feature, not a management tool.
• D (MDS Integration Service round robin): MDS Integration Service handles middleware/application connectivity, not BES administration across locations.

Memory tip: Think of BAS pooling like a "single pane of glass" - no matter how many cities your BES instances are in, the pool lets one admin console see and manage them all. If the question mentions managing across locations, the answer involves BAS pooling.

No community discussion yet for this question.