Free Workday Workday-Pro-HCM-Reporting Exam Questions & Answer from Training Expert SureTorrent [Q18-Q38]

Share

Free Workday Workday-Pro-HCM-Reporting Exam Questions and Answer from Training Expert SureTorrent

Top Workday Workday-Pro-HCM-Reporting Courses Online

NEW QUESTION # 18
You are creating a custom report that displays employee salary amounts. You need to ensure that compensation analysts have the appropriate security permissions to view this information for all employees.
How do you confirm the security group's access to salary amounts?

  • A. Review the domain security policy on the salary amount report field.
  • B. Run the Activate Security Policy Pending Changes task.
  • C. Assign individuals to the compensation analyst security group.
  • D. Review the domain security policy on the report's data source.

Answer: A

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


NEW QUESTION # 19
You are configuring a data column on a composite report. You would like to map a subreport prompt to a value in a prompt set, but the prompt is not appearing on the Map Sub Report Prompts grid in the column configuration options.
What could be causing this?

  • A. You already set a default value for the prompt on the subreport.
  • B. The Do Not Prompt at Runtime checkbox is selected for the prompt on the subreport.
  • C. You do not have access to the domain securing the report prompt.
  • D. You did not select Use Value From Prompt Set as the default prompt value in the subreport.

Answer: B

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


NEW QUESTION # 20
An HR analyst has many visualizations in different discovery boards that use the Workers for HCM Reporting data source on the Worker primary business object. The analyst wants to drill into one of the visualizations by Worker. Upon drilling, the analyst notices that Worker is not a listed Drill By field option. They want to drill by Worker without editing the Drill By list of the other visualizations.
How would the analyst configure this?

  • A. Create a control from a sheet filter and filter the data by Worker from the Control Panel.
  • B. Add Worker as a Drill By field from the Maintain Field Lists for Discovery Boards report.
  • C. Override the Drill By field list and add Worker in the Configuration Panel for this visualization.
  • D. Drag and drop the Worker field in one of the dimensions of this visualization in the Builder Panel.

Answer: C

Explanation:
In Discovery Boards, drill behavior is defined in the Drill By field list. To add Worker as a drillable option in just one visualization, the analyst can override the Drill By list in the Configuration Panel of that visualization. This allows Worker to appear as a drill dimension without altering the defaults applied across other visualizations.
From the Workday documentation: "You can override Drill By field lists in the visualization configuration panel. This enables drill customization on a per-visualization basis without impacting other discovery boards." The other options are less appropriate: Maintain Field Lists changes the default for all boards; adding Worker as a dimension affects grouping, not drilling; and sheet filter controls allow filtering but do not add drill options.
Thus, the correct choice is D. Override the Drill By field list and add Worker in the Configuration Panel for this visualization.


NEW QUESTION # 21
You configured a trending report for an HR analyst that shows headcount by country trends by quarter. The HR analyst has asked for the data to display for each month, rather than each quarter.
How can you fulfill these requirements?

  • A. Edit the Group by Time Period field in the report definition.
  • B. Run the Maintain Trended Workers task and modify the Trending Period.
  • C. Add a report prompt that uses the Trending Period field.
  • D. Edit the field on the Column Grouping grid in the report definition.

Answer: A

Explanation:
When designing trending reports, the Group by Time Period field determines how the trended records are aggregated and displayed. By default, reports may show quarterly or annual rollups, but this can be easily adjusted to monthly without 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 is B. Edit the Group by Time Period field in the report definition.


NEW QUESTION # 22
An HR analyst needs to schedule a collection of diversity reports to the HR director on a monthly basis. What mechanism should the HR analyst use to do this?

  • A. Alerts
  • B. Embedded analytics
  • C. Report groups
  • D. Report bursting

Answer: C

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.


NEW QUESTION # 23
You are creating a custom report to calculate the monthly bonus for each worker in the sales department. The bonus is calculated as 10% of the total sales for the month. What calculated field function would return the monthly bonus for each worker?

  • A. Evaluate Expression
  • B. Lookup Related Value
  • C. Sum Related Instances
  • D. Arithmetic Calculation

Answer: D

Explanation:
The Arithmetic Calculation function is designed for mathematical operations such as addition, subtraction, multiplication, and division. In this scenario, the bonus equals 10% of monthly sales, so you need to multiply the sales field by 0.10.
The Workday documentation highlights: "Arithmetic Calculation - Creates a numeric field using mathematical operations performed on existing fields." . This makes it the ideal choice for payroll- and incentive-related calculations.
Other options are less relevant: Evaluate Expression is for logical or Boolean conditions, Lookup Related Value is for retrieving fields from related objects (not calculations), and Sum Related Instances aggregates multiple rows of data but does not directly calculate percentages.
Thus, the arithmetic calculation provides a straightforward and efficient way to compute bonuses dynamically in the report.


NEW QUESTION # 24
A composite report sorts output based on the last column in ascending order. You want the sort to be based on the second to last column in descending order.
How do you make this change?

  • A. Edit the combine data row.
  • B. Create a dynamic data row.
  • C. Edit the second to last column.
  • D. Update the report settings.

Answer: C

Explanation:
Sorting in composite reports is determined at the column level, not at the combine row or general report settings. If the output currently sorts by the last column, that is because the sort option was applied there. To change the sorting behavior to the second-to-last column and in descending order, you must edit that specific column's configuration.
From the Workday binder: "Composite reports allow sorting based on columns. To change sorting behavior, adjust the column configuration, specifying ascending or descending order." The other options are incorrect: "combine data row" merges subreport outputs, not sorting; "dynamic data row" generates flexible rows but doesn't control sorting; and "report settings" manage prompts and scheduling, not output order.
Therefore, the correct action is B. Edit the second to last column.


NEW QUESTION # 25
Refer to the following scenario to answer the question below.
You have prepared the following matrix report for a recruiting manager.

The recruiting manager would like to view the top ten hiring sources, rather than just three.
How can you adjust the report definition to address this requirement?

  • A. Edit the Axis Scale on the Output tab.
  • B. Configure a Field Values group on the Group by Field.
  • C. Edit the Sort Rows field on the Row Grouping column.
  • D. Edit the Maximum Number of Rows field.

Answer: D

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


NEW QUESTION # 26
You have created a composite report and are trying to add a matrix report as a subreport. However, when trying to configure a Data column, the matrix report is not available to select in the Sub Report Name field.
What can you check to identify the cause of this issue?

  • A. Check that every field in the composite report's set of fields that are enabled for filtering and grouping also exists as a group-by field in the matrix report.
  • B. Check that the summarization fields in the matrix report also match the selections in the Field to Aggregate field in the Data column settings.
  • C. Check that the prompt defaults in the matrix report align with the prompt defaults defined in the composite report's Report Settings.
  • D. Check that the configurations on the Filter Data in Sub Report grid also exist in the Filter tab of the matrix report definition.

Answer: A

Explanation:
For a matrix report to be eligible as a subreport in a composite report, Workday requires strict alignment between the composite report's enabled fields and the matrix report's group-by fields. Specifically, every field enabled for filtering and grouping in the composite report must also exist as a group-by field in the matrix report.
If this alignment does not exist, Workday excludes the matrix report from the Sub Report Name selection list because the system cannot reliably aggregate or align the summarized data across reports.
Workday HCM Reporting documentation states:
"When using matrix reports as subreports in composite reports, the group-by fields must align with the composite report's enabled grouping and filtering fields."
"Matrix reports that do not meet grouping alignment requirements will not be available for selection as subreports." The other options do not control subreport eligibility:
Summarization fields affect calculations, not availability.
Filter alignment is validated later, not at selection time.
Prompt defaults do not determine whether a report appears in the Sub Report Name field.


NEW QUESTION # 27
The HR administrator is complaining about a report that is running slowly. The report uses the Trended Workers data source and includes a field on the related Worker business object.
How can you improve report performance without altering the report requirements?

  • A. Run the Create Worker Trending Data task.
  • B. Create a calculated field on the Trended Worker business object.
  • C. Run the Purge Worker Trending Data task.
  • D. Add the field to the Trended Workers data source.

Answer: D

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


NEW QUESTION # 28
An HR analyst has many visualizations in different discovery boards that use the Workers for HCM Reporting data source on the Worker primary business object. The analyst wants to drill into one of the visualizations by Worker. Upon drilling, the analyst notices that Worker is not a listed Drill By field option. They want to drill by Worker without editing the Drill By list of the other visualizations.
How would the analyst configure this?

  • A. Create a control from a sheet filter and filter the data by Worker from the Control Panel.
  • B. Add Worker as a Drill By field from the Maintain Field Lists for Discovery Boards report.
  • C. Override the Drill By field list and add Worker in the Configuration Panel for this visualization.
  • D. Drag and drop the Worker field in one of the dimensions of this visualization in the Builder Panel.

Answer: C

Explanation:
In Discovery Boards, drill behavior is defined in the Drill By field list. To add Worker as a drillable option in just one visualization, the analyst can override the Drill By list in the Configuration Panel of that visualization. This allows Worker to appear as a drill dimension without altering the defaults applied across other visualizations.
From the Workday documentation: "You can override Drill By field lists in the visualization configuration panel. This enables drill customization on a per-visualization basis without impacting other discovery boards." The other options are less appropriate: Maintain Field Lists changes the default for all boards; adding Worker as a dimension affects grouping, not drilling; and sheet filter controls allow filtering but do not add drill options.
Thus, the correct choice is D. Override the Drill By field list and add Worker in the Configuration Panel for this visualization.


NEW QUESTION # 29
You want the ability to view every summarization in the composite report by Location.
What do you do?

  • A. Include Location as a drillable field in all the subreports.
  • B. Include Location as a drillable field in one of the subreports.
  • C. Include Location as a Detail Data field in one of the subreports.
  • D. Include Location as a Detail Data field in all the subreports.

Answer: D

Explanation:
In composite reports, summarizations are driven by Detail Data fields provided by each subreport. If you want to summarize results consistently by Location across the entire composite report, Location must exist as a Detail Data field in every subreport.
Workday requires this consistency because composite-level summarizations rely on common fields across all subreports. If Location is missing from even one subreport's detail data, Workday cannot reliably aggregate or align summarizations by that field.
From the Workday HCM Reporting documentation:
"To summarize composite report data by a specific field, that field must be included as detail data in all subreports."
"Drillable fields enable navigation but do not support composite-level summarization." Including Location as drillable only affects drill-down behavior, not summarization. Including it in only one subreport results in incomplete aggregation.


NEW QUESTION # 30
You are configuring a data column on a composite report. You would like to map a subreport prompt to a value in a prompt set, but the prompt is not appearing on the Map Sub Report Prompts grid in the column configuration options.
What could be causing this?

  • A. You already set a default value for the prompt on the subreport.
  • B. The Do Not Prompt at Runtime checkbox is selected for the prompt on the subreport.
  • C. You do not have access to the domain securing the report prompt.
  • D. You did not select Use Value From Prompt Set as the default prompt value in the subreport.

Answer: B

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


NEW QUESTION # 31
You are building a composite report that uses two subreports with different data sources. You are noticing duplicate prompts when you run your composite report.
How can you resolve this problem?

  • A. Configure a prompt set on the composite report in the Report Settings.
  • B. Select the Do Not Prompt at Runtime for one of the duplicate prompts in the Report Settings.
  • C. Select the Do Not Prompt at Runtime checkbox for the overlapping prompts in each subreport.
  • D. Configure the same default value for each duplicate prompt.

Answer: A

Explanation:
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 a Prompt Set at 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 is A. Configure a prompt set on the composite report in the Report Settings.


NEW QUESTION # 32
Refer to the following scenario to answer the question below.
You have prepared the following matrix report for a recruiting manager.

The recruiting manager wants the rows to sort by Total Count, rather than Total Average Base Pay.
How can you adjust the report definition to address this requirement?

  • A. Add a new row to the grid on the Filter tab.
  • B. Reorder the rows in the Define the Field(s) to Summarize grid.
  • C. Adjust the Maximum Number of Rows value.
  • D. Add a new row to the grid on the Sort tab.

Answer: D

Explanation:
In Workday reporting, row ordering is controlled on the Sort tab of the report definition. If you want the rows in a matrix report to sort by a specific field (such as Total Count), you must add that field to the Sort tab. Filters limit records, and summarizations define metrics, but sorting rules are explicitly defined in the Sort configuration.
From the Workday Reporting documentation:
"Sort - Control the order to present and group data. You can specify options for subtotals, grand totals, and outlines. Add a row on the Sort tab to define sorting by a particular field." Therefore, to sort rows by Total Count instead of Total Average Base Pay, the correct step is C. Add a new row to the grid on the Sort tab.


NEW QUESTION # 33
A report that uses an indexed data source is running slowly for an HR analyst. The report is sorted by the Worker object field.
What can you do to improve the sorting performance?

  • A. Sort by the Full Name (text) field instead
  • B. Create a calculated field that only pulls the first name of the worker
  • C. Change the data source on the report
  • D. Select the Sort by First Accessible Column checkbox

Answer: A

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


NEW QUESTION # 34
Two people run the same report. One person can view all columns but the other person can only view some columns.
Why is the second user missing columns?

  • A. The second user is not the report owner.
  • B. The report uses an indexed data source.
  • C. The first user did not manually share the report with the second user.
  • D. The second user does not have access to the domain that secures the field.

Answer: D

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.


NEW QUESTION # 35
You only want to show snapshot data on a custom trending report that uses the Trended Workers data source.
How can you achieve this with minimal impact to report performance?

  • A. Run the Maintain Trended Workers task and configure the default record type.
  • B. Add a report filter using the Snapshot field.
  • C. Configure the default value of the Record Type prompt.
  • D. Use the Trended Workers for Planning data source filter.

Answer: B

Explanation:
The Trended Workers data source contains both snapshot records (period-end views of worker data) and event/transaction records (such as hires, terminations, and job changes). When the reporting requirement is to display only snapshot data, the most efficient and least disruptive approach is to apply a report-level filter using the Snapshot (or Record Type = Snapshot) field.
Workday HCM Reporting documentation explains that filtering at the report level allows the system to limit returned records without changing global trending configurations or requiring additional processing. This approach has minimal performance impact because it operates on already-generated trended data rather than forcing the system to recalculate or regenerate records.
Relevant documentation guidance includes:
"Trended Workers includes both snapshot and transaction records. Use report filters to restrict output to snapshot data when required."
"Avoid changing system-wide trending configurations when report-level filtering satisfies the business requirement." The other options are less appropriate:
Setting default prompt values still allows non-snapshot data to be retrieved.
Trended Workers for Planning is a different data source with a different purpose.
Running Maintain Trended Workers changes system configuration and impacts all trending reports.


NEW QUESTION # 36
You are configuring a waterfall visualization showing employee movement. To properly display the information, you need the Termination Count field to return as a negative number.

  • A. Numeric Constant
  • B. Format Number
  • C. Extract Single Instance
  • D. Arithmetic Calculation

Answer: D

Explanation:
When creating custom reports and visualizations, calculated fields can transform values. To change positive counts into negative values (such as terminations in a waterfall chart), you use the Arithmetic Calculation function. This function allows you to perform math operations (addition, subtraction, multiplication, division) on numeric fields. By multiplying the Termination Count by -1, the result displays as a negative number.
From Workday Reporting documentation:
"Arithmetic Calculation - Performs mathematical operations on numeric fields. You can create new numeric outputs such as percentages, ratios, or negatives by applying arithmetic logic." Thus, the correct answer is C. Arithmetic Calculation.


NEW QUESTION # 37
You want to view benefit cost by benefit enrollment for the current year compared to the prior year to evaluate increases or decreases in plan enrollment, displaying formatted cost and count variance calculations.
What type of report would allow you to do this?

  • A. Composite Report
  • B. Matrix Report
  • C. Trending Report
  • D. Advanced Report

Answer: C

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.


NEW QUESTION # 38
......

New (2026) Workday Workday-Pro-HCM-Reporting Exam Dumps: https://www.suretorrent.com/Workday-Pro-HCM-Reporting-exam-guide-torrent.html

Workday-Pro-HCM-Reporting Practice Dumps - Verified By SureTorrent Updated 61 Questions: https://drive.google.com/open?id=1rd453x_Z5XEBfiErWZzrP6RYO2GSXEVV