Which of the following components need to be added to ensure the report is point-in-time...

A point-in-time, static report represents:

Data as it existed at a specific time,

For a specific period,

And does not automatically update when underlying data changes.

To make this clear to readers:

You must show the time period the report covers (E)

e.g., “Q1 2025”, “1 Jan 2025 – 31 Mar 2025”.

This defines the scope of the data summarized in the report.

You must include the date on which the report was run (F)

e.g., “Report generated on: 15 Apr 2025”.

This shows the exact point in time at which the data was extracted and frozen.

Why the other options are not sufficient:

A. Control group for the phrases – is more about experimental design, not about making a report point-in-time.

B. Summary of the KPIs – useful, but does not establish time specificity or static nature.

C. Filter buttons for the status – implies interactivity, sometimes at odds with a static, frozen report.

D. Date when the report was last accessed – relates to user behavior (when someone opened it), not when the data snapshot was taken.

Therefore, to ensure the report is clearly point-in-time and static, you need E (time period covered) and F (date report was run).

CompTIA Data+ Reference (concept alignment):

DA0-001 Exam Objectives – Reporting: point-in-time vs real-time reporting.

CompTIA Data+ reporting best practices: including coverage period and run date to document the time context of reports.