BCP-620 · Question #16
Given the scenario, the administrator in the London office reports that sometimes after the BlackBerry Enterprise Server reboots, the following BlackBerry Enterprise Server components fail to start…
The correct answer is B. Install another Microsoft SQL Server at the London office and move the BlackBerry Configuration. Option B is correct because the root cause is a timing dependency issue: when BES reboots in London, its services attempt to connect to the SQL Server in New York before the network link is fully established, causing the startup failures. Moving the BlackBerry Configuration…
Question
Given the scenario, the administrator in the London office reports that sometimes after the BlackBerry Enterprise Server reboots, the following BlackBerry Enterprise Server components fail to start: the BlackBerry Dispatcher, BlackBerry Policy Service and BlackBerry Synchronization Service. They usually start after manually attempting to start them. This usually increases the BlackBerry Enterprise Server down time. Which troubleshooting step should be employed in this situation? (Choose one)
Options
- AInstall a standby BlackBerry Enterprise Server instance at the London site and configure the
- BInstall another Microsoft SQL Server at the London office and move the BlackBerry Configuration
- CSetup dependencies for all three services on the Microsoft SQL Server in the New York location
- DInstall another Microsoft SQL Server in the New York location and configure database mirroring for
- ESetup the Service Recovery 'First Failure' to restart the computer
How the community answered
(59 responses)- A2% (1)
- B75% (44)
- C15% (9)
- D5% (3)
- E3% (2)
Explanation
Option B is correct because the root cause is a timing dependency issue: when BES reboots in London, its services attempt to connect to the SQL Server in New York before the network link is fully established, causing the startup failures. Moving the BlackBerry Configuration Database to a local SQL Server in London eliminates the remote dependency, ensuring the database is immediately reachable when the BES services initialize.
Why the distractors are wrong:
- A (standby BES) adds redundancy but doesn't fix the startup timing problem on the primary server.
- C (setting service dependencies on New York SQL Server) is technically impossible - Windows service dependency chains only work for services on the same local machine, not remote servers.
- D (SQL Server mirroring in New York) keeps the database remote, doing nothing to resolve the cross-WAN connectivity delay during reboot.
- E (Service Recovery restart-computer on first failure) would trigger an endless reboot loop, making downtime dramatically worse.
Memory tip: When BES services fail on auto-start but succeed manually, think "the dependency isn't ready in time." The fix is always to bring the dependency closer (local SQL Server), not to add redundancy or restart the machine.
Topics
Community Discussion
No community discussion yet for this question.