A user is experiencing message delays on the BlackBerry device. When this occurs, the pending message count does not increase on the BlackBerry device users' statistics. What can be done during a…

Question

Options

• AReduce the network latency between the BlackBerry Enterprise Server and the Microsoft
• BChanging to another wireless service provider BlackBerry devices with better coverageChanging
• CReduce the network latency between the BlackBerry Enterprise Server and the Microsoft SQL
• DMove to a better performing Microsoft SQL Server
• EMake sure users remain in coverage during reported times

• A
  74% (17)
• C
  4% (1)
• D
  13% (3)
• E
  9% (2)

Explanation

Option A is correct because the symptom - delays without an increase in the pending message count - indicates that messages are not accumulating in the BES queue, meaning the bottleneck is upstream of the BES itself: specifically, the connection between the BlackBerry Enterprise Server and the Microsoft Exchange mail server. High network latency there means BES cannot fetch messages promptly, so they never enter the queue to be counted as pending.

Options B and E (wireless coverage/provider) address the device-to-BES leg of delivery - those issues would typically increase the pending count, because messages would be queued at BES waiting to reach a device, which is the opposite of what's described. Option C is a near-duplicate distractor that substitutes "SQL Server" for "Exchange"; SQL Server stores BES configuration and routing data, not the mail itself, so its latency wouldn't create this symptom pattern. Option D (a faster SQL Server) has the same flaw - improving database performance doesn't address mail-fetching delays between BES and Exchange.

Memory tip: Use the pending count as your directional clue - no increase means the delay is before the queue (BES ↔ Exchange), while an increase means the delay is after the queue (BES ↔ device). That maps directly to A vs. B/E.

No community discussion yet for this question.