500-601 · Question #25
During day-to-day operations, you notice that the HealthScore has decreased. What should you check first to understand what has impacted the score?
The correct answer is A. faults. Faults are the first place to look because they directly represent active problems - failed components, policy violations, or connectivity issues - that cause the HealthScore to drop. The HealthScore is essentially a real-time reflection of outstanding faults, so checking…
Question
Options
- Afaults
- Baudit logs
- Cevents
- Daccounting logs
How the community answered
(26 responses)- A88% (23)
- C8% (2)
- D4% (1)
Explanation
Faults are the first place to look because they directly represent active problems - failed components, policy violations, or connectivity issues - that cause the HealthScore to drop. The HealthScore is essentially a real-time reflection of outstanding faults, so checking faults gives you an immediate, targeted view of what is degrading the score.
Audit logs (B) record administrative actions by users (who changed what and when), which is useful for change tracking but won't explain a health degradation caused by system or network issues. Events (C) are broader informational notifications that may or may not correlate to health impact; they lack the direct severity-to-score mapping that faults provide. Accounting logs (D) track resource usage and billing data, which is entirely unrelated to health monitoring.
Memory tip: Think of it this way - Faults = problems the system found on its own. When health drops, something is broken, not just logged or counted. "Fault first" mirrors how you'd check a car's warning lights before digging through the maintenance history.
Topics
Community Discussion
No community discussion yet for this question.