Question 680
A dashboard tracks average resolution time but drops reopened cases from one month's denominator without disclosing the change. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.
Explanation
Correct Answers
Select history-aware analytics and explicit indicator definitions for trends, rather than claiming a one-time filtered list snapshot proves a sustained performance improvement. A current count is a point-in-time measure; a trend requires consistent observations and the same measurement definition over time. Verify prerequisites with: Inspect indicator source, collection cadence, historical baselines, aggregation definition, filter changes and denominator handling. Scenario: A dashboard tracks average resolution time but drops reopened cases from one month's denominator without disclosing the change.
Inspect indicator source, collection cadence, historical baselines, aggregation definition, filter changes and denominator handling. A current count is a point-in-time measure; a trend requires consistent observations and the same measurement definition over time. The appropriate response is: Select history-aware analytics and explicit indicator definitions for trends, rather than claiming a one-time filtered list snapshot proves a sustained performance improvement. Scenario: A dashboard tracks average resolution time but drops reopened cases from one month's denominator without disclosing the change.
Incorrect Answers
Build a dashboard from correctly scoped reports or visualizations and validate viewer access to underlying data and dashboard sharing before rollout. This step may apply to Dashboards and Platform Analytics audience permissions but is not one of the complementary requirements in this case. The intended pair is: Select history-aware analytics and explicit indicator definitions for trends, rather than claiming a one-time filtered list snapshot proves a sustained performance improvement. Together with: Inspect indicator source, collection cadence, historical baselines, aggregation definition, filter changes and denominator handling. Scenario: A dashboard tracks average resolution time but drops reopened cases from one month's denominator without disclosing the change.
An application incident can be traced through correct service relationships to affected service offerings and stakeholders. This step may apply to Common Service Data Model service relationships but is not one of the complementary requirements in this case. The intended pair is: Select history-aware analytics and explicit indicator definitions for trends, rather than claiming a one-time filtered list snapshot proves a sustained performance improvement. Together with: Inspect indicator source, collection cadence, historical baselines, aggregation definition, filter changes and denominator handling. Scenario: A dashboard tracks average resolution time but drops reopened cases from one month's denominator without disclosing the change.
Inspect event queue entry, event name/parameters, notification condition, recipient preferences, delivery state, and repeated event generation. This step may apply to Event-driven messaging and notification diagnostics but is not one of the complementary requirements in this case. The intended pair is: Select history-aware analytics and explicit indicator definitions for trends, rather than claiming a one-time filtered list snapshot proves a sustained performance improvement. Together with: Inspect indicator source, collection cadence, historical baselines, aggregation definition, filter changes and denominator handling. Scenario: A dashboard tracks average resolution time but drops reopened cases from one month's denominator without disclosing the change.


