Reports in Workday respect data source security constraints. Different users may see different results in the same report if their access is limited. For example, an HR analyst may have constrained access only to certain organizations or workers, while the Chief People Officer may also have constraints.
From Workday Reporting and Security documentation:
"Report results differ between users if security constraints apply. Constrained security groups grant access only to specific target data (e.g., workers in certain supervisory orgs), while unconstrained groups can view all data." Thus, the likely cause is that both the Chief People Officer and the HR analyst have constrained access to the data source. Correct answer: C.

When a report is scheduled to run at a recurring interval (daily, weekly, monthly, etc.), Workday tracks this under the Scheduled Future Processes report. This task allows administrators and report owners to view when reports are set to run, the frequency of execution, and the schedule start and end dates. If a report stopped running after the new year began, the most likely cause is that the scheduling end date expired on December 31, meaning no new jobs were generated for the new year.
From the Workday Reporting binder: "Workday provides scheduling options to run reports at set frequencies. You can confirm upcoming scheduled report runs in the Scheduled Future Processes report." This provides visibility into whether the report is still scheduled and when it is next expected to execute.
The other answers are incorrect: View Alerts relates to system notifications, Mass Operation Management is not for reporting, and Run History shows past runs but not future scheduling. The correct option is C. Scheduled Future Processes.

Composite reports combine multiple subreports, and their summarizations depend on the fields configured in the subreports themselves. To enable consistent grouping and summarization across the entire composite report, the Location field must be included as a Detail Data field in all the subreports. This ensures that each subreport provides the Location context required for composite-level summarization.
From the Workday binder: "Composite reports aggregate results from multiple subreports. To summarize or drill consistently on a specific field, that field must exist as a Detail Data field in all subreports included in the composite." If Location is only included in one subreport, summarizations in the other subreports would not align, and Location-based grouping would fail. Similarly, making Location drillable only affects drill-down options, not summary-level grouping across the composite.
Thus, the correct answer is A. Include Location as a Detail Data field in all the subreports.

To evaluate year-over-year changes in benefit costs and enrollments, you need historical data comparisons over time. The Trending Report type is designed for exactly this use case, leveraging data sources like Trended Workers to display snapshots at periodic intervals and calculate variances between time periods.
From the Workday binder: "Trending reports allow you to track changes to worker data across time. These reports support analysis of headcount, demographics, benefit enrollments, and cost variances year-over-year or month-over-month." Advanced and Matrix reports provide strong analysis capabilities, but they are based on current or related effective-dated data, not time-series snapshots. Composite reports combine multiple subreports but do not inherently manage trending data or variance calculations across years.
Therefore, the only correct option for year-over-year benefit enrollment and cost variance is D. Trending Report.

Report groups allow multiple reports to be bundled together and scheduled as a package to distribute at a set frequency. In this case, the HR analyst can group all diversity-related reports and schedule them to run automatically each month for the HR director.
The Workday documentation explains: "Workday provides additional reporting features such as sharing, scheduling, and exporting reports. Reports can be grouped into report groups for easier scheduling and delivery." .
While Report Bursting is used for distributing a single report with different data slices (e.g., sending each manager their team's results), it is not suited for bundling multiple different reports. Embedded analytics are dashboards, not scheduling tools. Alerts notify users of conditions but do not manage recurring report packages.
Therefore, Report Groups is the correct method for scheduling multiple reports together.