Several BlackBerry device users report messaging delays on their BlackBerry devices of greater than 10 minutes during core business hours. Management wants to know when this issue first occurred…

Question

Options

• ABlackBerry System Log Monitoring and Reporting tool
• BBlackBerry Message Flow Reporting tool
• CBlackBerry Enterprise Server User Administration tool
• DBlackBerry Enterprise Server Log Monitoring tool
• EBlackBerry Alert Service

• A
  8% (4)
• B
  72% (36)
• C
  2% (1)
• D
  14% (7)
• E
  4% (2)

Explanation

Option B is correct because the BlackBerry Message Flow Reporting tool is specifically designed to capture and store historical message delivery data - including timestamps - making it the right tool to review previously saved information and pinpoint exactly when messaging delays exceeded acceptable thresholds.

Why the distractors are wrong:

• A (System Log Monitoring and Reporting) focuses on system-level events and health metrics, not message flow timing data.
• C (User Administration tool) manages user accounts and device policies - it has no reporting capability for message delivery performance.
• D (Enterprise Server Log Monitoring) monitors server logs in real time or for server health; it is not purpose-built for tracking message flow delays historically.
• E (Alert Service) sends notifications when thresholds are breached going forward - it cannot retroactively show when a problem first started.

Memory tip: Think of "Message Flow" as a river with timestamps - the Message Flow Reporting tool records the journey of every message over time, so you can scroll back upstream to find exactly where and when the current slowed down.

No community discussion yet for this question.