The Primary Business Object (PBO) determines the primary instance for each row of the report. Since the requirement is to output "one row per worker," the Worker business object must be the PBO. The report needs to include fields (Name and Age) that exist on a different business object, Dependent. To access these fields from the Worker PBO, the Dependent business object must be included as a Related Business Object (RBO). This allows the report to pull in the multi-instance dependent data for each worker instance.

A. PBO: Dependent, RBO: Worker: This configuration would generate one row per dependent, which contradicts the requirement of one row per worker.

C. PBO: Dependent, no RBOs: This would incorrectly generate one row per dependent and would be unable to access any worker-specific information.

D. PBO: Worker; no RBOs: While the PBO is correct, this option would not allow the report to access the required Name and Age fields from the Dependent business object.

1. Workday Report Writer Documentation: "The primary business object determines what the report is about. Each instance of the primary business object will be a row in your report (before filtering)." This principle directly supports selecting Worker as the PBO to get one row per worker. The guide further explains

"To access fields on a different business object

you must relate to it from your primary business object or another related business object." This confirms the need for Dependent as an RBO. (Reference: Workday Report Writer Guide

Section: "Choosing a Data Source and Business Object").

2. Workday Business Objects Reference: The Worker business object documentation lists Dependents as a multi-instance related business object. This official data model confirms that to access fields on the Dependent object (like Name and Age) from a report based on Worker

one must traverse this relationship

making Dependent an RBO. (Reference: Workday Business Objects Documentation

Entry for "Worker" Business Object

Related Business Objects section).