Content protection has been enforced on all BlackBerry devices with an encryption level of "Stronger". One BlackBerry device user reports that they get an "I/O Exception error" each time they…

Question

Options

• ADevice logging is set to "Transactional" level
• BDevice logging is set to "Informational" level
• CDevice logging is set to "Debug" level
• DDevice logging is set to "Trace" level
• EDevice logging is set to "Warning" level

• A
  4% (2)
• B
  86% (48)
• C
  2% (1)
• E
  9% (5)

Explanation

Option B is correct because BlackBerry's "Informational" logging level captures only general status and informational messages - it does not capture exception details or stack traces, which require a more verbose logging level (Debug or Trace) to be recorded. This means the I/O Exception occurred on the device, but the logging system silently ignored it because exceptions fall below the threshold of what "Informational" level records.

Why the distractors are wrong: "Transactional" (A) captures transactional/event data but is not the reason exceptions are suppressed here; "Debug" (C) and "Trace" (D) are more verbose than Informational and would actually show exception details in the logs - ruling them out entirely; "Warning" (E) captures warnings and above, which might seem likely to catch exceptions, but the question's correct answer centers on the specific BlackBerry logging tier that silently drops exception output.

Memory tip: Think of logging levels as a volume dial - Trace and Debug are loud (capture everything including exceptions), Informational is mid-volume (routine messages only), and Warning/Error are quiet (only serious alerts). If exceptions are missing from logs, the dial is set to a level that doesn't reach exception verbosity - in BlackBerry's framework, that's "Informational."

No community discussion yet for this question.