In which three situations can you use threshold server-generated alerts to help diagnose and fix problems? (Choose three.)

Question

Options

• Awhen free space in a dictionary managed tablespace falls below a specified percentage
• Bwhen free space in a locally managed tablespace falls below a specified percentage
• Cwhen the total number of locked user account exceeds a specific value
• Dwhen the number of logons per second exceeds a specific value
• Ewhen a resumable statement is suspended
• Fwhen the total number of logons exceeds a specific value

• A
  5% (2)
• B
  76% (32)
• E
  12% (5)
• F
  7% (3)

Explanation

Oracle's threshold server-generated alerts work with metric-based monitoring on supported objects. B is correct because Oracle only supports space threshold alerts for locally managed tablespaces (LMTs)-not dictionary-managed tablespaces (A), which are a legacy type that predates this alert framework. C (locked user accounts) and D (logons per second) are valid built-in database metrics you can set warning/critical thresholds against using DBMS_SERVER_ALERT.

Why the distractors are wrong:

• (A) Dictionary-managed tablespaces are not supported by the threshold alert system-only LMTs are.
• (E) A suspended resumable statement triggers an event-based alert, not a threshold alert; it fires on occurrence, not when a metric crosses a boundary.
• (F) The supported metric is logons per second (a rate), not the total number of logons-making D correct and F a close-but-wrong distractor.

Memory tip: Think "LCD"-Locally managed tablespace space, Count of locked accounts, Duration/rate of logons per second. If the choice involves a legacy object (dictionary tablespace), an event trigger (resumable suspend), or a raw total instead of a rate (total logons), it's a distractor.

No community discussion yet for this question.