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

Answer : B

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

Answer : A

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 the Increment or Decrement Date function. 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 is A. Increment or Decrement Date.

Answer : B

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.

Answer : B

When reports use Indexed 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 by text-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

Answer : C

Workday offers several custom report types: Advanced, Matrix, Composite, Search, and Trending .

Advanced Reports: Allow sorting, filtering, grouping, totals, and charts but are not designed for percentage summarizations across grouped data.

Search Reports: Show search results based on facet filters, not suited for summarization and percentages.

nBox Reports: Used for displaying workers or positions across two dimensions (e.g., performance vs. potential).

Matrix Reports: Specifically designed for grouping data, applying summarizations (count, sum, percent), and drilling

Answer : A

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.

Answer : B

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.