Workday Pro HCM Reporting Online Practice Questions

Explanation:
Access to report fields in Workday is governed by security domains. If a user lacks access to the security domain that secures specific report fields, those fields will not appear in the report output for that user.
From the Workday Reporting documentation:
“A security group gets access to a security domain, which is a predefined set of related securable items. Securable items can include reports, tasks, data sources, and report fields.”
Therefore, the correct answer is C. The second user does not have access to the domain that secures
the field.

Explanation:
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.

Explanation:
The correct choice is Lookup Related Value, because this function allows you to retrieve a field from a related business object that is not directly stored on your primary object. In this scenario, the primary business object is Performance Review, which holds performance-related data but not job-related data such as Job Title. Since Job Title resides on the Worker business object, you need to link from Performance Review to Worker and then retrieve Job Title.
The Workday reporting guide explains: “Lookup Related Value C Returns a field from a related business object. Use this to bring data from associated objects into a report when the field is not directly available on the primary object.” . This ensures the Performance Review data can be combined with Job Title for meaningful insights.
By contrast, Aggregate Related Instances is used to roll up multiple related values, Range Band applies thresholds, and Evaluate Expression Band is used for conditional ranges, not cross-object retrieval.

Explanation:
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.

Explanation:
Workday report filters allow prompts so users can enter values when running a report. If the prompt value is left blank, Workday treats it as though no filter condition has been applied, so the system returns all available Worker instances regardless of the Location field.
From the Workday Reporting guide:
“Prompts C You can further narrow and refine your report results by having the user complete prompt fields before they run the report. You can set default values for prompts… If left blank, the filter condition is ignored and all data is returned.”
Therefore, the correct answer is D. All Worker instances, regardless of the value of the Location field.