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

If a recruiter sees an empty dashboard tile, the most likely cause is constrained security access . Even though the dashboard is properly configured and the worklet is enabled, Workday’s security framework ensures that report results vary by user depending on their role and assigned constraints.

From the Workday Reporting binder: “Report results differ between users if security constraints apply. Constrained security groups grant access only to a subset of data… Unconstrained security groups grant users access to all target instances of a securable item.” .

In this scenario, the recruiter likely has constrained access to only their supervisory organization or region. As a result, the “Top New Applications by Job Profile” report returns no records in the worklet tile.

Other options are less likely: if the recruiter lacked access to the report entirely, the tile would not appear; required vs. optional dashboard configuration would not impact existing data visibility; and domain-level security applies to report access, not data filtering.

Therefore, the correct answer is C. The recruiter has constrained access to the report's data source or data source filter .

Workday’s Report Performance Log highlights processing time contributors such as “Top Level Filter Time.” If this is high, the best practice is to replace report filters with built-in data source prompts , since prompts restrict data earlier in processing, improving performance.

From the Workday Reporting documentation:

“To improve report performance, leverage built-in data source prompts instead of filters whenever possible. Prompts reduce the data set retrieved before filters are applied, minimizing filter processing time.”

Therefore, the correct answer is B. Use built-in data source prompts instead of filters .

In Workday Discovery Boards, visualizations such as pivot tables are based on summarized and grouped data. When you choose to generate a report from a Pivot Table visualization , Workday converts the visualization into a Matrix Report that includes only a table , preserving the row and column groupings and summarizations used in the pivot.

The Workday HCM Reporting documentation states:

“When generating a report from a pivot table visualization, Workday creates a matrix report that reflects the grouped and summarized structure of the pivot.”

“Charts are not included when generating reports from pivot table visualizations; the output is a table-only matrix report.”

Advanced Reports are generated from non-pivot, row-based visualizations. XpressO is not used for discovery board–generated reports. Matrix reports with charts are created only when the visualization includes a chart component, which pivot tables do not.

Therefore, the correct answer is B. Matrix Report (with only a table) .

Performance issues often occur when trending reports pull fields from related business objects instead of directly from the Trended Workers data source . This requires Workday to join across objects at runtime, slowing down report execution. To improve performance, you should add 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 is A. Add the field to the Trended Workers data source .

In Workday, when you configure composite reports, you can map subreport prompts to prompt sets for greater flexibility. However, if the Do Not Prompt at Runtime checkbox is selected on the subreport prompt, the prompt will not be exposed in the Map Sub Report Prompts grid . This is because Workday interprets the prompt as suppressed and therefore not available for mapping at runtime.

From the Workday binder: “Prompts suppressed with the Do Not Prompt at Runtime option will not appear in the Map Sub Report Prompts grid in composite report configuration. To map a subreport prompt, ensure the prompt is enabled at runtime.”

Other options do not directly cause this issue: default values on prompts do not suppress them, security issues would block data but not hide the prompt mapping, and prompt set configuration errors affect defaulting but not visibility.

Thus, the correct answer is B. The Do Not Prompt at Runtime checkbox is selected for the prompt on the subreport .

In Workday matrix reports, the number of rows returned is controlled by the Maximum Number of Rows setting. By default, reports may limit output rows (for example, showing only the top 3). To display more results—such as the top 10 hiring sources—you must increase this value in the report definition.

From the Workday Reporting documentation:

“You can limit or expand the number of rows displayed in a matrix report by editing the Maximum Number of Rows field.”

“To display more than the default, update the value in the report definition.”

Therefore, the correct way to adjust this report to display the top 10 hiring sources is B. Edit the Maximum Number of Rows field .

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 .

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 .

The Record Type field in Trended Workers distinguishes between snapshots and transactions (such as hires, terminations, or transfers). To focus only on snapshot data, you can apply a report 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 is B. Add a report filter using the Snapshot field .

In Workday composite reports, sorting behavior is controlled at the column level , not globally. Each column in a composite report can be configured with its own sort order (ascending or descending). When a composite report is sorting by the last column, it means that column has an active sort configuration applied.

To change the sort to the second to last column and set it to descending , you must edit that specific column’s configuration and adjust the sort settings accordingly. Workday evaluates column sorting in sequence, and the active column-level sort determines the output order.

From the Workday HCM Reporting documentation:

“Composite reports support column-based sorting. Sorting is defined within the column configuration and determines the order in which results display.”

“To change sort behavior, update the sort settings on the appropriate column.”

The other options are incorrect because dynamic data rows control layout flexibility, combine data rows merge subreport results, and report settings manage prompts and general options—not sorting logic.

When ownership of a custom report is transferred in Workday, the system immediately evaluates whether the new report owner has full security access to all components of the report. This includes access to the data source , all report fields , calculated fields , and any secured domains referenced by the report. If the new owner lacks access to even one secured field or domain, the report becomes invalid for that owner.

The Custom Report Exception Audit report is specifically designed to identify these types of issues. A critical error appears when the report owner does not meet the minimum security requirements to maintain or run the report.

From the Workday HCM Reporting documentation:

“When transferring ownership of a custom report, the new owner must have access to all fields and data sources used in the report. If access is missing, the Custom Report Exception Audit will flag the report with an error.”

“Critical errors indicate security or configuration issues that must be resolved for the report to function correctly.”

The other options are incorrect because location has no impact on report ownership, prompts are supported in reports, and sharing controls visibility—not ownership validity.

Matrix reports in Workday allow for grouping, summarization, and drill-through capabilities. To let managers dynamically refine report results at runtime , you configure Facet 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 configure facet filters so 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 is D. Configure Facet Filters .

The True/False Condition calculated field is used to return Boolean results (True or False) based on defined criteria. In this scenario, the field must evaluate whether the event initiator equals the worker’s manager. By setting that condition, the calculated field will return True if the initiator is the manager and False otherwise.

From Workday Reporting documentation:

“True/False Condition – Creates a Boolean field that evaluates a condition and returns True or False depending on whether the condition is met.”

Thus, the correct answer is B. True/False Condition .

In Workday, access to sensitive data such as salary amounts is controlled at the report field level through security domains . Even if a user has access to the report itself or the data source, they will not be able to see secured fields unless their security group has permission to the domain that specifically secures that field .

The Workday HCM Reporting documentation explains that report fields are securable items and are governed by domain security policies. To confirm whether compensation analysts can view salary amounts for all employees, you must review the domain security policy associated with the Salary Amount report field and verify that the appropriate security group has View (or higher) access.

From the Workday documentation:

“Security access to report fields is controlled by domain security policies. Users must have access to the domain that secures a report field in order to view its data.”

“Even when users have access to a report or data source, secured fields will not display unless domain permissions are granted.”

Running Activate Security Policy Pending Changes applies changes but does not confirm access. Assigning users to a security group does not ensure that the group has the correct domain permissions. Reviewing only the data source security is insufficient because salary visibility is controlled at the field/domain level.