About this exam
Workday-Pro-Integrations is the Workday exam Workday Pro Integrations Certification Exam.
Paid practice material for this exam is not available yet, but you can try its free sample questions.
- Exam code
- Workday-Pro-Integrations
- Vendor
- Workday
- Practice questions
- Not available yet
- Free sample questions
- 8
- Question bank last updated
- Not available yet
Try 2 sample questions
Taken from the free sample set for Workday-Pro-Integrations.
Question 1
You need to filter a custom report to only show workers that have been terminated after a user prompted date.
How do you combine conditions in the filter to meet this requirement?
- AOption A:
Worker Status is equal to the value "Terminated" OR Termination Date is greater than a value
retrieved from a prompt
- BOption B:
Worker Status is equal to the value retrieved from a prompt AND Termination Date is less than a
value retrieved from a prompt.
- COption C:
Worker Status is equal to the value retrieved from a prompt OR Termination Date is equal to a
value retrieved from a prompt.
- DOption D:
Worker Statusis equal to the value "Terminated" AND Termination Date is greater than a value
retrieved from a prompt.
Show answer and explanation
Correct answer: D
The requirement is to filter a custom report to show only workers terminated after a user-prompted
date. In Workday, filters are defined in the Filter tab of the custom report definition, and conditions
can be combined using AND/OR logic to refine the dataset. Let’s analyze the requirement and
options:
Key Conditions:
Workers must be terminated, so the "Worker Status" field must equal "Terminated."
The termination must occur after a user-specified date, so the "Termination Date" must be greater
than the prompted value.
Both conditions must be true for a worker to appear in the report, requiring an AND combination.
Option Analysis:
A . Worker Status is equal to the value "Terminated" OR Termination Date is greater than a value
retrieved from a prompt: Incorrect. Using OR means the report would include workers who are
terminated (regardless of date) OR workers with a termination date after the prompt (even if not
terminated), which doesn’t meet the strict requirement of terminated workers after a specific date.
B . Worker Status is equal to the value retrieved from a prompt AND Termination Date is less than a
value retrieved from a prompt: Incorrect. Worker Status shouldn’t be a prompted value (it’s fixed as
"Terminated"), and "less than" would show terminations before the date, not after.
Question 2
You need to create a report that includes data from multiple business objects. For a supervisory
organization specified at run time, the report must output one row per worker, their active benefit
plans, and the names and ages of all related dependents. The Worker business object contains the
Employee, Benefit Plans, and Dependents fields. The Dependent business object contains the employee's dependent's Name and Age fields.
How would you select the primary business object (PBO) and related business objects (RBO) for the
report?
- AOption A:
PBO: Dependent, RBO: Worker
- BOption B:
PBO: Worker, RBO: Dependent
- COption C:
PBO: Dependent, no RBOs
- DOption D:
PBO: Worker; no RBOs
Show answer and explanation
Correct answer: B
In Workday reporting, selecting the appropriate Primary Business Object (PBO) and Related Business
Objects (RBOs) is critical to ensure that the report retrieves and organizes data correctly based on the
requirements. The requirement here is to create a report that outputs one row per worker for a
specified supervisory organization, including their active benefit plans and the names and ages of all
related dependents. The Worker business object contains fields like Employee, Benefit Plans, and
Dependents, while the Dependent business object provides the Name and Age fields for dependents.
Why Worker as the PBO?The report needs to output "one row per worker," making the Worker
business object the natural choice for the PBO. In Workday, the PBO defines the primary dataset and
determines the granularity of the report (i.e., one row per instance of the PBO). Since the report
revolves around workers and their associated data (benefit plans and dependents), Worker is the
starting point. Additionally, the requirementspecifies a supervisory organization at runtime, which is
a filter applied to the Worker business object to limit the population.
Why Dependent as an RBO?The Worker business object includes a "Dependents" field, which is a
multi-instance field linking to the Dependent business object. To access detailed dependent data
(Name and Age), the Dependent business object must be added as an RBO. This allows the report to
pull in the related dependent information for each worker. Without the Dependent RBO, the report
could only reference the existence of dependents, not their specific attributes like Name and Age.
Analysis of Benefit Plans:The Worker business object already contains the "Benefit Plans" field, which
provides access to active benefit plan data. Since this is a field directly available on the PBO (Worker),
no additional RBO is needed to retrieve benefit plan information.
Option Analysis:
A . PBO: Dependent, RBO: Worker: Incorrect. If Dependent were the PBO, the report would output one row per dependent, not one row per worker, which contradictsthe requirement. Additionally,
Worker as an RBO would unnecessarily complicate accessing worker-level data.
B . PBO: Worker, RBO: Dependent: Correct. This aligns with the requirement: Worker as the PBO
ensures one row per worker, and Dependent as the RBO provides access to dependent details (Name
and Age). Benefit Plans are already accessible via the Worker PBO.
C . PBO: Dependent, no RBOs: Incorrect. This would result in one row per dependent and would not
allow easy access to worker or benefit plan data, failing to meet the "one row per worker"
requirement.
D . PBO: Worker, no RBOs: Incorrect. While Worker as the PBO is appropriate, omitting the
Dependent RBO prevents the report from retrieving dependent Name and Age fields, which are
stored in the Dependent business object, not directly on Worker.
Implementation:
Create a custom report with Worker asthe PBO.
Add a filter for the supervisory organization (specified at runtime) on the Worker PBO.
Add Dependent as an RBO to access Name and Age fields.
Include columns from Worker (e.g., Employee, Benefit Plans) and Dependent (e.g., Name, Age).
Reference from Workday Pro Integrations Study Guide:
Workday Report Writer Fundamentals: Section on "Selecting Primary and Related Business Objects"
explains how the PBO determines the report’s row structure and RBOs extend data access to related
objects.
Integration System Fundamentals: Discusses how multi-instance fields (e.g., Dependents on Worker)
require RBOs to retrieve detailed attributes.
See all 8 free sample questions