Pass the Workday Human Capital Management Workday-Pro-HCM-Reporting Questions and answers with CertsForce

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.

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.

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.

When designing trending reports, theGroup by Time Period fielddetermines how the trended records are aggregated and displayed. By default, reports may show quarterly or annual rollups, but this can be easily adjusted tomonthlywithout needing to reconfigure or regenerate trending data.

From the Workday documentation:“In trending reports, the Group by Time Period setting allows users to choose the granularity of the results, such as monthly, quarterly, or annually. This setting controls the display of data in charts and tables.”

Other options are less appropriate: editing the Column Grouping grid changes report layout but not trending intervals, using a prompt does not change aggregation, and running the Maintain Trended Workers task changes system-wide trending setup, not individual report display.

Thus, the correct approach isB. Edit the Group by Time Period field in the report definition.

The correct choice isLookup 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, theprimary business object is Performance Review, which holds performance-related data but not job-related data such as Job Title. Since Job Title resides on theWorker 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.

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.

Workday maintains ashared WDSetup tenantwhere customers can access the latest delivered content, including reports, dashboards, and calculated field templates. Customers must log in through theWorkday Community portalto access this tenant.

From the Workday binder:“The WDSetup tenant provides shared configuration content maintained by Workday. Customers can access the tenant through Workday Community to review the latest delivered reports and dashboards.”

The other options are incorrect: Object Transporter (OX) migrates content between customer tenants, not WDSetup. Customer Central is a separate tenant for learning, not for content review. The “What’s New” report shows system updates, not the latest WDSetup content.

Therefore, the correct answer isC. Sign in to the Shared WDSetup tenant through the Workday Community.

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.

Enabling a report as a worklet and assigning it to a dashboard does not automatically make it visible. The Recruiting dashboard (or any dashboard in Workday) must beconfigured to include the workletexplicitly. This is a common oversight—report designers assume that enabling a report as a worklet is sufficient, but the dashboard itself must be updated in configuration to display that worklet tile.

From the Workday reporting materials:“Dashboards provide an interface to view multiple worklets. Even if a report is enabled as a worklet, the dashboard configuration determines which worklets are visible to end users.”

Other options are less relevant: exceeding 100 rows only impacts loading performance, not visibility; security issues would typically block data, not hide the worklet entirely; and required setup applies to whether the worklet is optional or required, but it must still be added to the dashboard.

Thus, the correct reason isB. You need to configure the Recruiting dashboard to include the worklet.

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