What can a Security Admin do in a situation where collecting additional log file information to examine a CloudGuard Controller issue is required?

Question

Options

• AExecute a debug on the SMS
• BSet the operation to TRACE to collect more data.
• CVerify connectivity between the SMS and the SDDC.
• DSearch for the information in the objects database.

• A
  15% (6)
• B
  77% (30)
• C
  5% (2)
• D
  3% (1)

Explanation

Setting the operation to TRACE is correct because CloudGuard Controller uses configurable logging levels, and TRACE is the most verbose level available - it captures detailed diagnostic data beyond what standard DEBUG or INFO levels provide, making it the appropriate tool when standard logs are insufficient to diagnose a controller issue.

Why the distractors are wrong:

• A (Execute a debug on the SMS) - "Debug" on the SMS is a general troubleshooting step unrelated to collecting granular CloudGuard Controller log data; the SMS and the CloudGuard Controller have separate logging mechanisms.
• C (Verify connectivity between SMS and SDDC) - This is a network connectivity check, useful for a different class of problem (communication failures), not for gathering deeper log information.
• D (Search the objects database) - The objects database stores configuration objects, not diagnostic log entries; it won't help you collect more runtime log data.

Memory tip: Think of logging levels as a dial - INFO → DEBUG → TRACE, each one louder than the last. When you need more data, you turn the dial up to TRACE. Associate "TRACE = maximum verbosity" and you'll immediately recognize it as the answer whenever a question asks about collecting additional log file information.

No community discussion yet for this question.