If each international office has its own standalone BlackBerry Administration Service installed, what should be taken into consideration when creating a failover pool? (Choose one)

Question

Options

• AThe fact that only one BlackBerry Exchange Server can run the BlackBerry Administration Service
• BThe fact that only one BlackBerry Administration Service can run as primary and the others must
• CThe network connectivity between the offices
• DThe fact that the BlackBerry Administration Service must be installed on a messaging server
• EThe number of BlackBerry device users logging into the BlackBerry Administration Service

• B
  3% (1)
• C
  84% (32)
• D
  5% (2)
• E
  8% (3)

Explanation

When creating a failover pool across international offices, network connectivity (C) is the critical factor because failover pools require BAS instances to communicate with each other to detect failures and transfer control - poor or unreliable WAN links between offices can prevent a failover from triggering correctly or completing successfully.

Why the distractors fail:

• A is incorrect because multiple BAS instances can co-exist; there's no restriction tying a single BAS to one BlackBerry Exchange Server.
• B describes normal failover pool behavior (one primary, others secondary) - that's expected design, not a consideration unique to this scenario.
• D is incorrect because BAS is a standalone service and does not need to reside on a messaging server.
• E relates to capacity planning, not failover pool architecture.

Memory tip: Picture the offices as nodes in a network diagram. Before worrying about roles (primary vs. secondary) or user counts, ask "Can these nodes actually talk to each other?" - that's always the first question in any geographically distributed failover design.

No community discussion yet for this question.