Workday-Pro-HCM-Reporting Workday Pro HCM Reporting Certification Exam Questions and Answers

Matrix reports in Workday allow grouping of data, applying summarizations, and drilling into the summaries for deeper analysis . To calculatepercentages relative to the overall total, Workday provides a built-in summarization option called“Percent of Overall Total.”This option is applied to numeric summarizations like “Number of Hires.”

From the Workday Reporting Guide:

“Matrix reports allow you to group data, summarize the metrics for each grouping, and drill into the summarizations for further analysis.”

“You can apply different summarizations such as Count, Sum, Average, andPercent of Overall Totalon numeric fields.”(Matrix Report Options – Workday Module 1 Binder)

Therefore, to show thepercentage of hires per recruiter relative to the grand total across recruiters and regions, you would select“Percent of Overall Total”on the Number of Hires summarization.

Workday’s configurable security model determines how much data a user can see in reports. If a user can only see their direct reports, they currently haveconstrained access. To view performance data for all workers, the user requiresunconstrained accessto the data source tied to the report field.

From Workday security documentation:

“Constrained security groups grant members access only to a subset of data… Unconstrained security groups grant users access to all target instances of a securable item.”

Therefore, the user needsD. Unconstrained access to the data source used in the report.

TheTrended Workersdata source is specifically designed for reports that displaytrends over time, such as headcount, turnover, and demographics. It captures periodicsnapshots of worker data(monthly, quarterly, etc.), which allows organizations to track workforce metrics historically.

From the Workday binder:“Trended Workers captures snapshots of worker data at periodic intervals, providing historical reporting across time dimensions. This enables reporting on headcount, attrition, and demographics in a time series format.”

By contrast,Workers for HCM Reportingis used for current-state data, not trending.Worker Historyprovides effective-dated transaction-level history but does not automatically generate trending snapshots.Headcountis a standard delivered report and not a reusable data source for custom trending analysis.

Therefore, the most appropriate data source for worker headcount trends over time isA. Trended Workers.

Workday calculated fields allow users to manipulate dates, numbers, and text values. To calculate a new date based on an existing date field (e.g., Bonus Approval Date), you use theIncrement or Decrement Datefunction. This adds or subtracts a defined number of days, months, or years from the source date.

From Workday Reporting documentation:

“Increment or Decrement Date – Returns a date that is a specified number of days, months, or years before or after the value of the source date field.”

Example: If the Bonus Approval Date is 01/01/2025, adding 60 days using this function would return 03/02/2025.

Thus, the correct choice isA. Increment or Decrement Date.

When using multiple subreports in a composite report, duplicate prompts often occur if both subreports request similar information (e.g., Company, Date, or Supervisory Organization). The best practice in Workday is to configure aPrompt Setat the composite level. Prompt sets allow you to consolidate duplicate prompts into one, mapping the same input across multiple subreports.

From the Workday documentation:“Composite reports allow prompt consolidation through Prompt Sets. Configure prompt sets in the composite report’s Report Settings to eliminate duplicate prompts and provide a streamlined user experience.”

Other answers are less efficient: assigning the same default value does not eliminate duplication, suppressing prompts with “Do Not Prompt at Runtime” removes flexibility for end users, and handling only one duplicate prompt does not consolidate across subreports.

Therefore, the correct solution isA. Configure a prompt set on the composite report in the Report Settings.

Access to report fields in Workday is governed bysecurity 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, andreport fields.”

Therefore, the correct answer isC. The second user does not have access to the domain that secures the field.

TheLookup Related Valuefunction retrieves a value from a related business object. Since Compensation Group is not stored directly on the Worker object but instead through theJob Profilebusiness object, this function lets you traverse the relationship to return the related field into your report.

From Workday Reporting documentation:

“Lookup Related Value – 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.”

Therefore, the correct answer isC. Lookup Related Value.

TheRecord Type fieldin Trended Workers distinguishes between snapshots and transactions (such as hires, terminations, or transfers). To focus only on snapshot data, you can apply areport filter on the Snapshot field, ensuring only monthly or quarterly snapshots are displayed. This approach improves report performance because filtering happens at the report level without modifying global trending settings.

From the Workday reporting documentation:“Trended Worker data includes snapshots and transactions. To restrict a report to snapshots, apply a filter on the Record Type or Snapshot field.”

Other answers involve system-wide changes or unnecessary complexity: running Maintain Trended Workers redefines system defaults, configuring prompts adds user interaction overhead, and Trended Workers for Planning is a different data source intended for forecasting.

Thus, the most efficient option isB. Add a report filter using the Snapshot field.

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, theLocation 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 isA. Include Location as a Detail Data field in all the subreports.

Matrix reports in Workday allow for grouping, summarization, and drill-through capabilities. To let managersdynamically refine report results at runtime, you configureFacet Filters. Facet Filters enable users to filter the report output interactively, without modifying the underlying definition.

From the Workday Reporting documentation:

“Matrix reports allow grouping and summarization of data. You can also configurefacet filtersso users can dynamically refine report results by selecting values such as Hiring Source or Location.”

Thus, the correct way to let the recruiting manager refine the output isD. Configure Facet Filters.

When reports useIndexed Data Sources, performance issues can arise if sorting is attempted on fields that are not indexed. In the case of the Worker object, sorting directly by the Worker object field is slower. Workday best practice is to sort bytext-based fields such as the “Full Name (text)” field, which improves query performance because it leverages indexed fields.

From the Workday reporting materials:

*“For indexed data sources, performance improves when sorting by text fields such as Full Name (text), instead of object fields. Sorting by object fields causes slower performance, whereas text-based fields use the

Performance issues often occur when trending reports pull fields from related business objects instead of directly from theTrended Workers data source. This requires Workday to join across objects at runtime, slowing down report execution. To improve performance, you shouldadd the required field to the Trended Workers data source, ensuring the data is pre-joined and optimized for trending.

From the Workday binder:“To improve performance, add commonly reported fields directly to the Trended Workers object. Using related business object fields requires additional joins and increases report runtime.”

Creating calculated fields adds complexity rather than improving speed. Purging or re-creating trending data maintains system hygiene but does not address field-level performance.

Thus, the correct solution isA. Add the field to the Trended Workers data source.