Workday-Pro-HCM-Reporting Exam Dumps

Workday provides multiple types of data sources when creating reports. Among them, Indexed Data Sources are specifically designed for performance optimization on large data volumes. They allow faster retrieval and better scalability when working with high record counts, because they are pre-optimized for reporting and queries.

From the Workday Reporting guide:

''Indexed data sources provide optimized performance for large data volumes. These data sources are indexed on commonly used fields and are specifically designed to support high-performance queries.''

Thus, the correct choice is A. Indexed for ensuring performance with large datasets.

Matrix reports in Workday allow grouping and summarization of data, but to drill down through hierarchical structures such as supervisory organizations, you must configure hierarchy-aware calculated fields. The Lookup Hierarchy Rollup function enables drillable hierarchies, showing performance metrics at each level of the organizational tree.

The Workday binder notes: ''Matrix reports allow you to group data, summarize the metrics for each grouping, and drill into the summarizations for further analysis.'' . This means you can expand results from the top supervisory org down to teams and individual workers.

Using a simple Lookup Related Value would only pull in one field from a related object, not enable hierarchical drill-down. Similarly, changing sort order or adding overrides does not create drillable hierarchies. Only Lookup Hierarchy Rollup enables this behavior.

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.

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.

The Trended Workers data source is specifically designed for reports that display trends over time, such as headcount, turnover, and demographics. It captures periodic snapshots 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 Reporting is used for current-state data, not trending. Worker History provides effective-dated transaction-level history but does not automatically generate trending snapshots. Headcount is 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 is A. Trended Workers.