Oracle 1Z0-1046-25 Online Practice Questions and Exam Preparation

Oracle 1Z0-1046-25 Online Questions & Answers

• Question 121:

  Your users have commented that time to assign an Area of Responsibility is wasted, due to the fact that they have to keep adding the same scope to several users, and were wondering if there was functionality to allow for scopes to be preset and used multiple times. How can this be achieved?

  A. Areas of Responsibility Templates
  B. Areas of Responsibility Preferences
  C. Areas of Responsibility Duplication
  D. Areas of Responsibility Default Settings
  A. Areas of Responsibility Templates

  ---

  In Oracle HCM Cloud,Areas of Responsibility (AOR) Templatesallow administrators to predefine AOR scopes (e.g., departments, locations) and reuse them across multiple users. This feature, accessible via the Manage Areas of Responsibility task, streamlines assignment by saving common configurations as templates, reducing repetitive manual entry. Users can then apply these templates when assigning AORs, meeting the requirement for preset, reusable scopes. Option B (Preferences) relates to user settings, not AOR configuration. Option C (Duplication) isn't a formal feature-duplicating AORs is manual. Option D (Default Settings) doesn't exist for AORs. Option A correctly identifies AOR Templates as the solution, per Oracle's functionality.

  References: Oracle Docs - "Implementing Global Human Resources" (docs.oracle.com, published 2023-12-12), Areas of Responsibility section.

• Question 122:

  When initiating the Change Manager transaction for employees, the first-level approval is assigned to the HR Specialist Sales application role. In the approval rule configuration for Change Manager, the option to Enable Auto Claim is not selected. What happens in this case?

  A. The transaction goes for approval to all the workers who inherit the HR Specialist Sales role and one of the HR Specialist Sales representatives needs to "Claim" the transaction for it to be assigned for approval
  B. The transaction has to be approved by all HR Specialist Sales representatives for it to be approved; if one of the HR Specialist Sales representatives rejects the transaction, others can still approve it
  C. The transaction goes for approval to all the workers who inherit the HR Specialist Sales role; the transaction will be auto-claimed and assigned randomly to anyone who has the HR Specialist Sales role
  D. The transaction goes into error because it was not auto-claimed and if one of the HR Specialist Sales representatives rejects the transaction, others can still approve it
  A. The transaction goes for approval to all the workers who inherit the HR Specialist Sales role and one of the HR Specialist Sales representatives needs to "Claim" the transaction for it to be assigned for approval

  ---

  In Oracle HCM Cloud's BPM Worklist, when an approval task (e.g., Change Manager) is assigned to an application role like "HR Specialist Sales" with multiple inheritors, the "Enable Auto Claim" setting determines assignment behavior. If Auto Claim is disabled (not selected), the task is sent to all users with the role as a shared notification. One of these users must manually "Claim" the task in the worklist to take ownership and proceed with approval or rejection. Until claimed, the task remains unassigned to

  a specific individual, ensuring only one approver acts after claiming.

  Option B (all must approve) misrepresents the process-only one approval is needed post-claim. Option C (auto-claimed randomly) contradicts the disabled Auto Claim setting. Option D (error) is incorrect-disabling Auto Claim doesn't cause errors; it just requires manual claiming. Option A accurately describes the behavior: the task goes to all HR Specialist Sales role holders, and one must claim it, per Oracle's approval framework.

  References: Oracle Docs - "Using Global Human Resources" (docs.oracle.com, published 2023-10-03), Approval Rules section.

• Question 123:

  A human resource specialist is promoting an employee. While promoting an employee, the human resource specialist is required to enter the promotion date, promotion action, and promotion reason. However, the promotion reason list of values does not list an appropriate reason.

  Which two options can help the human resource specialist understand the Action framework available in the application?

  A. Actions are seeded and cannot be defined by a user.
  B. Action Types are seeded and cannot be defined by a user.
  C. Action Reasons are seeded and cannot be defined by a user.
  D. Action Reasons are seeded and can be defined by a user.
  B. Action Types are seeded and cannot be defined by a user.
  D. Action Reasons are seeded and can be defined by a user.

  ---

  The Action framework in Oracle HCM Cloud consists of Action Types, Actions, and Action Reasons:

  B: True-Action Types(e.g., Promotion, Termination) are seeded by Oracle and cannot be user-defined, providing a fixed categorization structure.

  D: True-Action Reasons(e.g., "Career Advancement") include seeded values but can be user-defined via Manage Action Reasons, allowing customization to meet specific needs like the missing promotion reason.

  A: False-Actions (e.g., "Internal Promotion") can be user-defined and linked to seeded action types.

  C: False-Action Reasons are customizable, not fully seeded.

  Options B and D clarify the framework's flexibility and constraints, helping the specialist address the issue per Oracle's documentation.

  References: Oracle Docs - "Implementing Global Human Resources" (docs.oracle.com, published 2023-12-12), Actions Configuration section.

• Question 124:

  Manage Legal Entity

  Scenario

  The newly acquired company that manufactures spring hinges for spectacles in Michigan will be its own legal entity. You need to create a legal entity for this company.

  Task

  Create a legal entity in the HCM system that will be its own Payroll Statutory Unit, where:

  1. The name of the legal entity is x Cloud vision

  2. The identifier is xCLDVIS

  3. The legal address is, as previously created

  4. The EIN or TIN is 93654213. 5.

  The Legal Reporting Unit Registration Number is 1212321.

  A. See the solution in explanation below.
  B. PlaceHolder
  C. PlaceHolder
  D. PlaceHolder
  A. See the solution in explanation below.

  ---

  This task requires creating a legal entity in Oracle Global Human Resources Cloud for a newly acquired company, x Cloud Vision, that manufactures spring hinges for spectacles in Michigan. The legal entity must also be its own Payroll Statutory Unit (PSU), with specific details provided: name, identifier, legal address (previously created), EIN/TIN, and Legal Reporting Unit Registration Number. Below is a verified, step-bystep solution based on Oracle's official documentation, ensuring accuracy and compliance with the system's functionality as of the latest releases

  Step-by-Step Solution

  Step 1: Log in to Oracle Fusion Applications

  Action: Log in to Oracle Fusion Applications using a user account with privileges such as Application Implementation Consultant or HCM Application Administrator. These roles grant access to the Setup and Maintenance work area.

  The Setup and Maintenance work area is the central hub for configuration tasks, including managing legal entities. The user must have permissions to access the Workforce Structures functional area and the Manage Legal Entity task. Roles like Application Implementation Consultant include the necessary privileges (e.g., Manage Legal Entity duty role).

  Verification: Oracle documentation confirms that setup tasks require specific security roles, and the Manage Legal Entity task is restricted to authorized users.

  Oracle Global Human Resources Cloud: Implementing Global Human Resources, Section: Security for Setup Tasks.

  Step 2: Navigate to Setup and Maintenance

  Action: From the Oracle Fusion Applications home page, click the Navigator icon (hamburger menu) in the top-left corner.

  Under the Tools section, select Setup and Maintenance.

  The Setup and Maintenance work area provides access to all implementation and configuration tasks, organized by functional areas. This is the entry point for accessing the Manage Legal Entity task.

  Verification: Oracle's user interface consistently places Setup and Maintenance under the Navigator's Tools section, as confirmed in both Redwood and responsive interfaces.

  Oracle Global Human Resources Cloud: Implementing Global Human Resources, Section: Setup and Maintenance Overview.

  Step 3: Select the Workforce Structures Functional Area and Locate the Task

  Action: In the Setup and Maintenance work area, click the Functional Area dropdown and select Workforce Structures.

  In the task list, locate Manage Legal Entity by scrolling or using the search bar (type "Manage Legal Entity").

  Click the Go to Task icon (typically a play button or arrow) next to Manage Legal Entity to open the task.

  The Workforce Structures functional area includes tasks related to organizations, including legal entities. The Manage Legal Entity task is designed to create and manage legal entities, including their attributes and associations. Using the search bar ensures quick access if the task list is extensive.

  Verification: Oracle documentation lists Manage Legal Entity under Workforce Structures, accessible via the Setup and Maintenance UI in both Redwood and responsive interfaces.

  Oracle Global Human Resources Cloud: Using Global Human Resources, Section: Manage Legal Entity.

  Step 4: Initiate Creation of a New Legal Entity

  Action: On the Manage Legal Entity page, click the Create button (typically a plus sign (+) or labeled "Create" in the Redwood interface).

  This opens the Create Legal Entity page for entering the legal entity details.

  The Manage Legal Entity page displays a searchable list of existing legal entities. The Create action starts the process of adding a new legal entity, opening a form where details like name, identifier, and address can be entered.

  Verification: Oracle's UI for managing legal entities includes a Create button, as confirmed in documentation and Redwood interface updates (24C and later).

  Oracle Global Human Resources Cloud: Implementing Global Human Resources, Section:Creating Legal Entities.

  Step 5: Enter the Legal Entity Details

  Action: On the Create Legal Entity page, enter the following details as provided in the scenario:

  Name: Enter x Cloud Vision.

  Legal Entity Identifier: Enter xCLDVIS.

  Country: Select United States from the dropdown list.

  Legal Address: Search for and select the previously created address: 900 Main St, Dearborn Heights, Wayne, Michigan 48127.

  Click the Search icon (magnifying glass) in the Legal Address field.

  Enter Dearborn Heights or 900 Main St in the search criteria and click Search.

  Select the address and click OK.

  EIN or TIN: Enter 93654213x.

  Legal Reporting Unit Registration Number: Enter 1212321x.

  Organization Type: Select Legal Employer (as the legal entity is a company with employees).

  Effective Start Date: Enter 04/15/2025 (current date, unless the acquisition date is specified; adjust if a specific date is required).

  Payroll Statutory Unit: Check the box for Payroll Statutory Unit or select Yes to designate the legal entity as its own PSU.

  Name: The legal entity name must be x Cloud Vision, matching the scenario exactly for identification.

  Legal Entity Identifier: xCLDVIS is a unique code for the legal entity, used in system processes and reporting.

  Country: United States is required, as the address is in Michigan.

  Legal Address: The address (900 Main St, Dearborn Heights, Wayne, Michigan 48127) was created in a previous task and must be selected to link it to the legal entity. The search ensures the correct address is used.

  EIN or TIN: 93654213x is the Employer Identification Number or Tax Identification Number, used for tax reporting.

  Legal Reporting Unit Registration Number: 1212321x identifies the legal reporting unit for compliance purposes.

  Organization Type: Legal Employer is appropriate, as the company employs workers (implied by manufacturing operations).

  Effective Start Date: Oracle uses effective dating to track legal entity validity. The current date (04/15/2025) is used unless otherwise specified.

  Payroll Statutory Unit: Designating the legal entity as a PSU ensures it handles its own payroll reporting and compliance, as required by the scenario. This creates a PSU automatically tied to the legal entity.

  Verification: Oracle documentation specifies mandatory fields (e.g., Name, Country, Address) and optional fields (e.g., EIN/TIN) for legal entity creation. The Payroll Statutory Unit option is explicitly supported, and the provided details align with US legal entity requirements.

  Oracle Global Human Resources Cloud: Using Global Human Resources, Section: Legal Entity Fields.

  Step 6: Configure Additional Settings (if prompted)

  Action: Jurisdiction: If prompted, select United States, Michigan as the jurisdiction for compliance with state regulations.

  Payroll Statutory Unit Details: If a PSU section appears, confirm the PSU name (defaults to x Cloud Vision ) and ensure the EIN or TIN and Registration Number are carried over.

  Primary Legal Address: Verify that 900 Main St, Dearborn Heights, Wayne, Michigan 48127 is marked as the primary legal address (typically automatic).

  Jurisdiction: Michigan is the appropriate jurisdiction for a US-based company in Dearborn Heights.

  PSU Details: Creating a PSU requires minimal additional input, as the legal entity's details (e.g., EIN/TIN) are reused.

  Primary Legal Address: Oracle requires at least one primary address for compliance; the selected address fulfills this role.

  Verification: Oracle documentation confirms that PSU creation can be integrated with legal entity setup, and jurisdiction and address settings are standard fields.

  Oracle Global Human Resources Cloud: Implementing Global Human Resources, Section:Payroll Statutory Units.

  Step 7: Save the Legal Entity

  Action: After entering all details, click Save and Close (or Save if further edits are needed).

  If prompted, confirm the creation of the legal entity and PSU.

  Saving creates the legal entity and, if selected, the associated PSU in the system. The Save and Close button finalizes the task, while Save allows additional configurations (e.g., adding more addresses).

  Oracle validates mandatory fields before saving.

  Verification: Oracle's UI includes Save and Save and Close options for legal entity creation, as confirmed in documentation for both responsive and Redwood interfaces.

  Oracle Global Human Resources Cloud: Implementing Global Human Resources, Section: Saving Legal Entities.

  Step 8: Verify the Legal Entity Creation

  Action: Return to the Manage Legal Entity page.

  In the search criteria, enter x Cloud Vision or xCLDVIS and click Search.

  Confirm that the new legal entity appears with the details:

  Name: x Cloud Vision

  Identifier: xCLDVIS

  Legal Address: 900 Main St, Dearborn Heights, Wayne, Michigan 4812. EIN or TIN: 93654213. Legal Reporting Unit Registration Number: 1212321. Payroll Statutory Unit: Yes

  Effective Start Date: 04/15/202. Optionally, verify the PSU by navigating to the Manage Payroll Statutory Units task and searching for x Cloud Vision.

  Verification ensures the legal entity and PSU were created correctly. Searching by name or identifier confirms the record's accuracy and checks for errors. Checking the PSU separately validates its creation if required.

  Verification: Oracle documentation emphasizes verifying setup tasks by searching created records, and the Manage Legal Entity page supports detailed searches.

  Oracle Global Human Resources Cloud: Using Global Human Resources, Section: Searching Legal Entities.

  Detailed

  Purpose of Legal Entity: A legal entity represents a registered organization for compliance, tax, and payroll purposes. x Cloud Vision as a legal employer and PSU ensures it handles its own workforce and reporting obligations.

  Payroll Statutory Unit: Designating the legal entity as a PSU means it acts as the entity responsible for payroll calculations and statutory reporting (e.g., W-2 forms in the US). This aligns with the scenario's requirement for independence.

  Legal Address Integration: The address (900 Main St, Dearborn Heights, Wayne, Michigan 48127) links the legal entity to its physical or registered location, critical for compliance. The prior creation of this address ensures it is available for selection.

  EIN/TIN and Registration Number: The EIN/TIN (93654213x) and Legal Reporting Unit Registration

  Number (1212321x) are unique identifiers for tax and reporting, formatted as per US requirements.

  Redwood Interface: In the Redwood interface (24C and later), the Manage Legal Entity page may feature enhanced UI elements (e.g., streamlined forms, inline validation), but the core fields and steps remain consistent with the responsive interface.

  Effective Dating: The effective start date ensures the legal entity is active from the specified date, supporting future changes (e.g., address updates).

  Key Considerations

  Accuracy: All details (x Cloud Vision, xCLDVIS, 93654213x, 1212321x) must be entered exactly as provided to avoid errors in reporting or compliance.

  Address Availability: The legal address must exist in the system. If not found, revisit the Manage Legal Addresses task to create it first.

  PSU Creation: Checking the PSU box automatically creates a PSU linked to the legal entity, reusing the provided EIN/TIN and registration number unless overridden.

  Security: Only users with the Manage Legal Entity privilege can perform this task. Role mismatches require administrative intervention.

  Jurisdiction: Selecting United States, Michigan ensures compliance with state-specific regulations, though it may be optional in some configurations.

  Potential Challenges and Solutions

  Access Denied: If the user lacks the Manage Legal Entity privilege, an error occurs. Solution: Assign the Application Implementation Consultant role via Security Console.

  Address Not Found: If the address (900 Main St) is missing, the system prevents saving. Solution: Create the address using the Manage Legal Addresses task before proceeding.

  Duplicate Identifier: If xCLDVIS already exists, an error occurs. Solution: Search for the identifier first; if it exists, coordinate with the implementation team to resolve conflicts.

  Redwood UI Variations: The Redwood interface may use different button labels (e.g., Add instead of Create ) or layouts. Solution: Follow field prompts and ensure all required fields are completed.

  PSU Configuration: If PSU creation prompts additional fields, use default values derived from the legal entity unless specified. Solution: Confirm EIN/TIN and registration number alignment.

  References

  Oracle Global Human Resources Cloud: Implementing Global Human Resources, Document ID: docs.oracle.com, Published: 2023-12-1. Section: Manage Legal Entity: "Steps to create legal entities, including name, identifier, address, and PSU designation."

  Section: Payroll Statutory Units: "Explains how legal entities can be configured as PSUs for payroll reporting."

  Oracle Global Human Resources Cloud: Using Global Human Resources, Document ID: docs.oracle.com, Published: 2024-07-02

  Section: Creating Legal Entities: "Details on entering legal entity attributes and linking addresses."

  Section: Legal Entity Compliance: "Importance of EIN/TIN and registration numbers."

  Oracle Fusion Cloud Human Resources 24C What's New, Document ID: docs.oracle.com, Published:2024-08-27 Creatures of the Void: A Journey into the Unknown Creatures of the Void: A Journey into the Unknown

  Section: Redwood Experience for Workforce Structures: "Enhanced UI for legal entity and address management."

  Oracle Fusion Cloud Human Resources 25A What's New, Document ID: docs.oracle.com, Published:2025-03-2. Section: Workforce Structures: "Streamlined legal entity setup with PSU integration.

• Question 125:

  What work area within HCM Cloud provides implementers with end-to-end access to all configuration objects needed to successfully implement HCM Cloud: Core HR?

  A. Person Management work area
  B. Enterprise Structures work area
  C. Workforce Structures work area
  D. Setup and Maintenance work area
  D. Setup and Maintenance work area

  ---

  TheSetup and Maintenance work area(FSM) in Oracle HCM Cloud is the central hub for implementers, providing comprehensive access to all configuration tasks required for implementing Core HR. This includes defining enterprise structures, workforce structures, geographies, and other foundational elements. While the Person Management (A), Enterprise Structures (B), and Workforce Structures (C) work areas support specific functions, they are operational or subset areas, not the end-to-end

  configuration hub. The Oracle "Implementing Global Human Resources" guide confirms that FSM is the primary work area for Core HR setup, makingDthe correct answer.

  Oracle HCM Cloud: Implementing Global Human Resources, "Setup and Maintenance Overview".

• Question 126:

  An HR representative enters employee details in the application as part of the hiring process. On the Review page, the HR representative notices that Person Number does not show any number, but indicates "Generated Automatically." Identify the option that relates to this intended behavior.

  A. Person Number at the Enterprise Level is set to Manual.
  B. Person Number at the Enterprise Level is set to Automatic before submission.
  C. Person Number at the Enterprise Level is set to Automatic after final save.
  D. Worker Number at the Enterprise level is set to Manual.
  C. Person Number at the Enterprise Level is set to Automatic after final save.

  ---

  Person Number in Oracle HCM Cloud is a unique identifier for individuals, and its generation method is configured at the enterprise level via the "Manage Enterprise HCM Information" task. The behavior described-showing "Generated Automatically" with no number until the final save-indicates a specific setting. Option C ("Person Number at the Enterprise Level is set to Automatic after final save") is correct. When configured this way, the Person Number is not assigned during data entry or review but is

  generated only after the transaction is fully saved. This ensures the number is allocated only when the record is committed, avoiding unused numbers if the process is abandoned. The "Implementing Global Human Resources" guide explains this option under Person Number generation settings.

  Option A ("Person Number at the Enterprise Level is set to Manual") would require manual entry, not automatic generation.

  Option B ("Person Number at the Enterprise Level is set to Automatic before submission") would assign the number earlier, visible during review, contradicting the scenario.

  Option D ("Worker Number at the Enterprise level is set to Manual") is irrelevant, as "Worker Number" is not a standard term here; it's Person Number.

  References:

  "Oracle Global Human Resources Cloud: Implementing Global Human Resources" - Section on Enterprise HCM Information, Person Number setup.

  "Oracle Human Resources Cloud: Using Global Human Resources" - Hiring process details.

• Question 127:

  Which three options define Enterprise Structures Configurator (ESC)? (Choose three.)

  A. After defining the enterprise structure and the job/position structures, the administrator can review them, make any necessary changes, and then load/rollback the final configuration
  B. The tool creates a structure of divisions that may then be manipulated by the administrator
  C. The tool creates a structure of divisions, legal entities, business units, and departments
  D. The tool creates a structure of divisions, legal entities, business units, and reference data sets
  E. It is an interview-based tool that guides through the process of setting up a basic enterprise structure
  A. After defining the enterprise structure and the job/position structures, the administrator can review them, make any necessary changes, and then load/rollback the final configuration
  D. The tool creates a structure of divisions, legal entities, business units, and reference data sets
  E. It is an interview-based tool that guides through the process of setting up a basic enterprise structure

  ---

  The Enterprise Structures Configurator (ESC) in Oracle Global Human Resources Cloud is detailed in the "Implementing Global Human Resources" guide:

  Option A: True. ESC allows review, modification, and load/rollback of the enterprise and job/position structures.

  Option B: False. ESC doesn't limit to divisions; it includes broader structures.

  Option C: False. Departments are not a primary output; reference data sets are included instead.

  Option D: True. ESC creates divisions, legal entities, business units, and reference data sets.

  Oracle Global Human Resources Cloud - Implementing Global Human Resources, "Enterprise Structures Configurator Overview" section.

• Question 128:

  As a consultant in your company, you are required to set up names and details of schools, colleges, universities, and so on, so that users can select from this list when entering their qualifications such as degrees. Identify the correct setup task in Functional Setup Manager > Define Workforce Profiles.

  A. Define Talent Profile Content > Manage Profile Content Items
  B. Define Talent Profile Content > Manage Content Subscribers
  C. Define Talent Profiles > Manage Profile Types
  D. Define Talent Profile Content > Manage Educational Establishments
  D. Define Talent Profile Content > Manage Educational Establishments

  ---

  In Oracle Global Human Resources Cloud, educational establishments (schools, universities) are maintained as part of the talent profile to support qualification tracking.

  Option A: "Manage Profile Content Items" defines specific content (e.g., skills), not educational institutions.

  Option B: "Manage Content Subscribers" controls access to content, not the list itself.

  Option C: "Manage Profile Types" defines profile structures, not specific data likeinstitutions.

  Option D: Correct. "Manage Educational Establishments" under Define Talent Profile Content allows setup of a selectable list of schools, colleges, and universities for qualifications.

  The correct answer isD, per "Implementing Global Human Resources" on workforce profiles.

  References: Oracle Global Human Resources Cloud - Implementing Global Human Resources, Chapter 13: Workforce Profiles.

• Question 129:

  A multinational construction company, headquartered in London, has operations in five countries. It has its major operations in the UK and US and small offices in Saudi Arabia, UAE, and India. The company employs 3,000 people in the UK and US and 500 people in the remaining locations. The entire workforce in India falls under the Contingent Worker category. How many Legislative DataGroups (LDGs), divisions, legal employers, and Payroll Statutory Units (PSUs) need to be configured for this company?

  A. Four LDGs (UK, US, India, and one for Saudi Arabia and UAE combined), five divisions (one for each country), four legal employers (all except India), and five PSUs.
  B. Five LDGs (one for each country), four divisions (UK, US, India, and one for Saudi Arabia and UAE combined), two legal employers and PSUs (US and UK only, because the workforce is very small in the other countries).
  C. Five LDGs, five divisions, five legal employers, and five PSUs.
  D. Five LDGs (one for each country), four divisions (UK, US, India, and one for Saudi Arabia and UAE combined), five legal employers, and four PSUs (all except India).
  D. Five LDGs (one for each country), four divisions (UK, US, India, and one for Saudi Arabia and UAE combined), five legal employers, and four PSUs (all except India).

  ---

  In Oracle Global Human Resources Cloud, enterprise structures like LDGs, divisions, legal employers, and PSUs are configured based on legislative, operational, and payroll needs.

  LDGs: One per country (UK, US, Saudi Arabia, UAE, India) due to distinct legislative requirements (e.g., labor laws, tax rules), totaling 5.

  Divisions: Operationally, the company can group Saudi Arabia and UAE into one division due to their small size, alongside UK, US, and India, totaling 4 divisions.

  Legal Employers: Each country typically requires a legal employer for employees (UK, US, Saudi Arabia, UAE). India's contingent workers still require a legal employer for compliance, totaling 5.

  PSUs: Payroll Statutory Units are needed for payroll processing. India's contingent workers may not require a PSU if payroll is not processed (common for contingent workers), so 4 PSUs (UK, US, Saudi Arabia, UAE).

  Option A: Incorrect; combining Saudi Arabia and UAE into one LDG ignores separate legislative needs.

  Option B: Incorrect; only 2 legal employers and PSUs overlook small offices' compliance needs.

  Option C: Incorrect; 5 PSUs assume India needs payroll, which isn't typical for contingent workers.

  Option D: Correct: 5 LDGs, 4 divisions, 5 legal employers, 4 PSUs.

  The correct answer isD, per "Implementing Global Human Resources" on enterprise structures.

  References: Oracle Global Human Resources Cloud - Implementing Global Human Resources, Chapter 2:Enterprise Structures.

• Question 130:

  Which four objects are keyed by a Reference Data Set to allow sharing and restricting of values between business units, such as Department and Location?

  A. Jobs
  B. Actions
  C. Positions
  D. Grades
  E. Location
  F. Departments
  A. Jobs
  D. Grades
  E. Location
  F. Departments

  ---

  Reference Data Sets (RDS) in Oracle HCM Cloud control the sharing and restriction of reference data across

  business units. The four objects keyed by RDS include:

  Jobs (A): Shared or restricted by business unit for employment consistency.

  Grades (D): Linked to compensation and restricted by RDS.

  Location (E): Physical work locations shared or restricted via RDS.

  Departments (F): Organizational units managed via RDS for segregation.

  Oracle HCM Cloud: Implementing Global Human Resources, "Reference Data Sets".