156-915.77 · Question #203
(Topic 16) If Jack was concerned about the number of log entries he would receive in the SmartReporter system, which policy would he need to modify?
The correct answer is D. Consolidation Policy. See the full explanation below for the reasoning.
Question
- (Topic 16)
If Jack was concerned about the number of log entries he would receive in the SmartReporter system, which policy would he need to modify?
Options
- ALog Sequence Policy
- BReport Policy
- CLog Consolidator Policy
- DConsolidation Policy
How the community answered
(34 responses)- A9% (3)
- B15% (5)
- C3% (1)
- D74% (25)
Community Discussion
6
Dejan C.Jun 27, 2026The correct answer is D, Consolidation Policy. SmartReporter pulls raw logs from the Log Server and runs them through its consolidation engine before generating report data, and it is the Consolidation Policy that controls how those raw log records get merged, aggregated, and filtered down into the consolidated log database. If Jack is drowning in entries, the problem is upstream of the report generation step itself, meaning the Report Policy only controls how final reports are formatted and scheduled, not how many underlying records feed into them. Tighten the Consolidation Policy rules, for example by adjusting the time intervals or the matching criteria used to collapse similar connections into single entries, and the volume of records landing in the SmartReporter database drops accordingly.
Nina C.Jun 20, 2026The answer is D, Consolidation Policy, because that is the policy inside SmartReporter that controls which log records actually get stored into the reporting database and how they get grouped together before storage. Think of it this way: the Consolidation Policy is like the filter that sits upstream of your reports, so if Jack is drowning in log entries, that is the knob he needs to turn, not the Report Policy which just formats what is already stored. I actually saw this exact scenario on my exam and my first instinct was B because "report" was right there in the question context, but then I remembered that the Report Policy only defines the layout and scheduling of reports, it does not touch the volume of raw log data feeding into SmartReporter. Once I recalled that the Consolidation Policy is what decides how logs get aggregated and filtered before they hit the database, D was the obvious pick and I went with it confidently.
Viktor S.Jun 22, 2026Good instinct on the upstream versus downstream framing, but calling Consolidation Policy a "filter" undersells it, because the aggregation side is actually what kills Jack's volume problem, since filtering alone still leaves you with thousands of near-duplicate records if your grouping rules are not set correctly.
Ola B.Jun 22, 2026The wording on this one is a little sloppy because "Log Consolidator Policy" in option C sounds like exactly what you want, and I have seen people pick it on instinct, but that option does not actually exist as a named policy in SmartReporter. The Consolidation Policy is the real control point where you tune how log entries get merged and reduced before they hit your reports, so D is your answer here.
Nina C.Jun 23, 2026Good catch on the trap wording, and I will add that this is exactly the kind of distractor that gets you if you are skimming fast, because "Log Consolidator Policy" has just enough real-sounding pieces to feel right when you are under time pressure.
Viktor S.Jun 27, 2026D is right, but do you actually know what a Consolidation Policy consolidates and why it cuts log volume?