Given the scenario, if the company decided to deploy another BlackBerry Administration Service in North America to make it highly available, with the knowledge that all the administration for the…

Question

Options

• ADeploy another BlackBerry Administration Service in the London location
• BDeploy another BlackBerry Administration Service in the Vancouver location
• CDeploy another BlackBerry Administration Service in the Los Angeles location
• DDeploy another BlackBerry Administration Service in the New York location

• A
  4% (1)
• B
  8% (2)
• C
  13% (3)
• D
  75% (18)

Explanation

Deploying the second BlackBerry Administration Service (BAS) in New York (D) is best practice because high availability components should be co-located with the administrators who use them. Since all North American administration originates from New York, placing the secondary BAS there ensures administrators experience low latency and uninterrupted access during a failover - defeating the purpose of HA if the backup node is unreachable or slow.

Why the distractors fail:

• A (London) - Outside North America entirely; irrelevant to a North America HA deployment and would introduce significant WAN latency for NY-based admins.
• B (Vancouver) - While in North America, it is geographically distant from the NY admin team, adding unnecessary latency and complexity.
• C (Los Angeles) - Also North America, but still far from New York; proximity to the administrators, not just the users, is what matters for a BAS.

Memory tip: Think "admin tools follow the admins, not the users." BlackBerry devices may be spread across many locations, but the BAS serves the administrator - so always place HA pairs where the administrators sit.

No community discussion yet for this question.