1Z0-1046-25 Real Exam Questions and Verified Answers

Question 1 Single choice

In order for a worker to complete a checklist item before their hire date, the following must be done?

A
The worker must have been added as an applicant in Recruiting Cloud
B
The worker needs to be added as an Employee with a future hire date
C
The worker must be added as a Pending Worker with an effective date equal to or less than the system date and a future hire date

Show answer and explanation

Correct answer: C

Explanation

Checklists in Oracle Global Human Resources Cloud can be assigned to workers before their official hire date, typically during onboarding. The "Using Global Human Resources" guide under "Checklists and Onboarding" explains that for a worker to access and complete checklist tasks prior to their hire date, they must be added as a Pending Worker. A Pending Worker record requires an effective date (start date of the record) that is equal to or earlier than the current system date, allowing system access, and a future hire date (when they transition to an Employee). This setup enables pre-hire tasks, such as completing forms, to be actioned.
Option A (applicant in Recruiting Cloud) doesn't grant HCM access, and Option B (Employee with future hire date) doesn't allow pre-hire task completion before the hire date is effective.
Option C is precise and correct.
References:
Oracle Global Human Resources Cloud - Using Global Human Resources, "Pending Workers
and Checklists" section.

Question 2 Single choice

Your customer wants to leverage the Tree Manager functionality to meet their Security and Reporting requirements. You discuss the delivered hierarchies to help them choose the correct tree structure.

Which option represents seeded tree structures?

A
Organization, job, division, geographies
B
Organization, position, division, establishment
C
Organization, position, department, geographies
D
Organization, job, department, geographies
E
Organization, position, division, geographies

Show answer and explanation

Correct answer: C

Explanation

Comprehensive and Detailed Explanation From Exact Extract: In Oracle Global Human Resources Cloud, the Tree Manager functionality is used to define and manage hierarchical structures that support security, reporting, and organizational requirements. Seeded tree structures are predefined hierarchies provided by Oracle to help organizations model their workforce structures efficiently. These seeded structures are designed to align with common organizational components and are available out-of-the-box for configuration.
According to the official Oracle HCM Cloud documentation, the seeded tree structures in Oracle Global Human Resources Cloud are: Organization: Represents the organizational hierarchy, such as business units, legal entities, or departments.
Position: Defines the position hierarchy, which outlines reporting relationships based on job roles or positions within the organization.
Department: Represents the departmental hierarchy, which organizes employees into functional or operational units.
Geographies: Defines geographic hierarchies, such as country, region, or city, used for location-based reporting and compliance.
The exact extract from the Oracle documentation states: "You can define trees to create hierarchical structures to reflect your organization for reporting and security purposes. Examples of predefined tree structures include organization, position, department, and geographies. Use trees to create a hierarchical representation of the structure that is used for approvals, reporting, and security." This confirms that the seeded tree structures are organization, position, department, and geographies, making option C the correct answer.
Why the other options are incorrect: Option A (Organization, job, division, geographies): This is incorrect because job is not a seeded tree structure. Jobs represent roles or functions but are not used to define hierarchies in Tree Manager.
Additionally, division is not a predefined tree structure in Oracle HCM Cloud. Option B (Organization, position, division, establishment): This is incorrect because division and establishment are not seeded tree structures. While organizations may use custom hierarchies for divisions or establishments, they are not part of the predefined seeded structures.
Option D (Organization, job, department, geographies): This is incorrect because job is not a seeded tree structure, as explained in
option A.
Option E (Organization, position, division, geographies): This is incorrect because division is not a seeded tree structure, as explained in
option B.

References:
Oracle Help Center, Using Global Human Resources, Chapter: Workforce Structures, Topic: Trees (https:// docs.oracle.com/en/cloud/saas/human-resources/25b/global-human-resources/using-global-human- resources/index.html) Oracle HCM Cloud Documentation, Implementing Global Human Resources, Chapter: Workforce Structures, Section: Managing Trees (https://docs.oracle.com/en/cloud/saas/human-resources/25b/global-human-resources/implementing-global-human-resources/index.html)

Question 3 Multiple choice

The Human Resource Representative of the organization is trying to set up the Jobs and Positions for the enterprise.

What are the three options that the Human Resource Representative should be aware of regarding Jobs and Positions? (Choose three.)

A
When using positions, the grades that are specified for the job become the default grades for the position
B
Jobs and Positions are shared by Sets
C
Jobs are shared by Sets and Positions are assigned to Business Units
D
Positions may be added to a specific department and location

Show answer and explanation

Correct answers: A, C, D

Explanation

Per the "Managing Workforce Structures" guide: Option A: True. Grades defined for a Job default to the Position when created.
Option B: False. Jobs are Set-enabled, but Positions are tied to business units, not shared by Sets.
Option C: True. Jobs are shared across Sets; Positions are specific to Business Units.

References:
Oracle Global Human Resources Cloud - Managing Workforce Structures, "Jobs and Positions
Configuration" section.

Question 4 Single choice

When creating a checklist task, you must assign a task performer.

What values are supported?

A
Worker, Manager, Initiator, User, Area of Responsibility
B
Worker, Manager, Initiator, User, Area of Responsibility, HR Specialist Job Role
C
Worker, Manager, Initiator, Area of Responsibility
D
Worker, Manager, Initiator, User, HR Specialist Data Role

Show answer and explanation

Correct answer: A

Explanation

When configuring checklist tasks in Oracle Global Human Resources Cloud, a task performer must be assigned to indicate who is responsible for completing the task. The "Using Global Human Resources" guide under "Checklists" specifies the supported performer types as: Worker (the individual the checklist pertains to), Manager (the worker's line manager), Initiator (the person who triggered the checklist), User (a specific named user), and Area of Responsibility (a group defined by responsibility criteria, such as HR representatives).
Option A lists all five supported values accurately.
Option B adds "HR Specialist Job Role," which is not a directly supported performer type for checklists (job roles are used in security, not task assignment).
Option C omits "User," and Option D incorrectly includes "HR Specialist Data Role" instead of "Area of Responsibility." Thus, A is the correct answer.
References:
Oracle Global Human Resources Cloud - Using Global Human Resources, "Configuring
Checklist Tasks" topic.

Question 5 Single choice

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

Show answer and explanation

Correct answer: A

Explanation

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 6 Single choice

A Human Resource Specialist is hiring a new employee in the application. While creating the employee record, he enters personal information and employment details and, when submitting the transaction, encounters an error. Part of the error message reads: "NewPersonEmploymentApproval to NewPersonEmploymentApproval Rules NewPersonRuleSet failed with Business Fault: null. Check the underlying fault. Check target SOA component for cause." The Human Resource Specialist raises a service request with the internal support team.

What is the cause of this error?

A
A security profile needs to be defined for the Human Resource Specialist to hire a person.
B
The BPM task NewPersonEmploymentApproval is not set up properly.
C
The Human Resource Specialist does not have the required privilege for the New Person Employment process.
D
The Update Person Keyword Search process must be run before hiring a person.

Show answer and explanation

Correct answer: B

Explanation

The error message indicates a failure in the approval process during the "New Person Employment" transaction, pointing to an issue with the BPM (Business Process Management) workflow rather than security or pre-process requirements.
Option A: Security profiles control data visibility, not approval process execution. Thiswouldn't cause a
BPM fault.
Option B: Correct. The error references "NewPersonEmploymentApproval," a BPM task. A "Business Fault: null" suggests a misconfiguration in the approval ruleset (e.g., missing approver, invalid rule) within BPM Worklist, preventing the transaction from completing.
Option C: Lack of privilege would typically block access to the hire action entirely, not trigger a mid-process BPM fault.
Option D: The "Update Person Keyword Search" process enhances search functionality but is unrelated to hiring approvals.
The correct answer isB, as detailed in "Implementing Global Human Resources" under Approval Configuration.

References:
Oracle Global Human Resources Cloud - Implementing Global Human Resources, Chapter 3:
Approvals and Notifications.

Question 7 Single choice

As an implementation consultant, you realize during the Requirement Gathering phase of your project that some Actions are not required.

How will you make these Actions unavailable for the end user?

A
Educate users not to use such Actions.
B
Delete Actions.
C
Enter Action End Date.
D
Hide Actions.

Show answer and explanation

Correct answer: C

Explanation

In Oracle Global Human Resources Cloud, Actions (e.g., Hire, Transfer) are managed via the "Manage Actions" task. To make an Action unavailable, you must ensure it's not accessible to users without deleting
it, preserving data integrity.
Option A: Educating users is not a system-enforced solution and risks accidental use.
Option B: Deleting Actions is not recommended post-implementation, as it can disrupt historical data or references; it's also not always possible for seeded Actions.

Option C: Correct. Setting an Action End Date (via Manage Actions) marks the Action as inactive from that date onward, preventing users from selecting it in transactions while retaining its history. This is the standard method to disable Actions.
Option D: Hiding Actions via UI tools (e.g., Page Composer) is possible but not a direct Action management feature; it's less reliable than end-dating.
The correct answer isC, as per "Implementing Global Human Resources" on Action management.

References:
Oracle Global Human Resources Cloud - Implementing Global Human Resources, Chapter 6:
Actions and Action Types.

Question 8 Lab simulation

Simulation

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 93654213x
5. The Legal Reporting Unit Registration Number is 1212321x

Show answer and explanation

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.
Explanation: 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.
Explanation: 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.
References:
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.
Explanation: 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.
Reference: 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.
Explanation: 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).
Reference: 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.
Explanation: 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.
Reference: 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).
Explanation:
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.
References:
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.
Explanation: 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.
Reference: 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 48127
EIN or TIN: 93654213x
Legal Reporting Unit Registration Number: 1212321x
Payroll Statutory Unit: Yes
Effective Start Date: 04/15/2025
Optionally, verify the PSU by navigating to the Manage Payroll Statutory Units task and searching for x
Cloud Vision.
Explanation: 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.
Reference: Oracle Global Human Resources Cloud: Using Global Human Resources, Section: Searching
Legal Entities.
Detailed Explanation
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-12
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-20
Section: Workforce Structures: "Streamlined legal entity setup with PSU integration.

Question 9 Multiple choice

For the Change Manager transaction, the first-level approval is set to the Application Role type. The name of the application role is HR Specialist Sales. In the Change Manager approval rule configuration, the Enable Auto Claim option is deselected.

Which two actions take place when the transaction for manager change is initiated for employees?

A
The transaction goes into error because it was not auto-claimed
B
The transaction has to be approved by all HR Specialist Sales representatives for it to be approved
C
The transaction goes for approval to all the workers who inherit the HR Specialist Sales role
D
One of the HR Specialist Sales representatives should "Claim" the transaction for it to be assigned for approval

Show answer and explanation

Correct answers: C, D

Explanation

In Oracle Global Human Resources Cloud, approval rules for the Change Manager transaction are configured per the "Securing HCM" guide: With "Enable Auto Claim" deselected, the transaction isn't automatically assigned to one approver; it goes to all users with the HR Specialist Sales role (Option C).
References:
Oracle Global Human Resources Cloud - Securing HCM, "Approval Rules Configuration" topic.

Question 10 Single choice

Your organization needs to download a large number of document record and their attachments for specific document type (degree or certificate).
If you want to limit the mass download to only this document type, how would you configure it in HCM Cloud: Global Human Resources?

A
On the Document Type setup page, select the "permitted for mass download" field on the document type of Degree or Certificate.
B
Configure the "HCM Flow and Document Type Mapping" section on the HCM Data Loader Template setup page by adding a row for permitted document type, and select Degree or Certificate.
C
Configure the "HCM Flow and Document Type Mapping" section on the Enterprise HCM Information setup page by adding a row for permitted document type, and select Degree or Certificate.

Show answer and explanation

Correct answer: A

Explanation

The organization needs to download a large number of document records and their attachments for specific document types (Degree or Certificate) and limit the mass download to only these types. The question asks how to configure this in Oracle HCM Cloud.
Option A: On the Document Type setup page, select the "permitted for mass download" field on the document type of Degree or Certificate.This is the correct answer. Oracle HCM Cloud allows mass download of document records and attachments via the Document Records page or related processes. To restrict downloads to specific document types, the Manage Document Types task includes a Permitted for Mass Download field (introduced in recent releases, e.g., 24C). By enabling this field for the Degree and Certificate document types, you ensure that only records of these types are included in mass download operations, meeting the requirement to limit the scope.
Option B: Configure the "HCM Flow and Document Type Mapping" section on the HCM Data Loader Template setup page by adding a row for permitted document type, and select Degree or Certificate.This option is incorrect. The HCM Data Loader (HDL) is used for importing and exporting data, including document records, but it does not have an HCM Flow and Document Type Mapping section specifically for configuring mass downloads. While HDL supports document record imports, the configuration for mass download restrictions is managed at the document type level, not through HDL templates, making this option invalid. Option C: Configure the "HCM Flow and Document Type Mapping" section on the Enterprise HCM Information setup page by adding a row for permitted document type, and select Degree or Certificate.This option is incorrect. The Enterprise HCM Information task configures enterprise-level settings (e.g., working hours, person number generation), but it does not include an HCM Flow and Document Type Mapping section or any settings for document type download restrictions. Mass download permissions are controlled via document type setup, not enterprise settings, ruling out this option. Why this answer?The Permitted for Mass Download field on the Document Type setup page directly controls which document types can be included in mass download operations, ensuring that only Degree and Certificate records are downloaded. This aligns with Oracle's configuration model for document management, making A the correct choice.

References:
Oracle Global Human Resources Cloud: Using Global Human Resources, Document ID: docs. oracle.com,
Published: 2024-07-02
Section: Manage Document Types: "Configure the Permitted for Mass Download field to restrict which document types can be downloaded in bulk."
Oracle Fusion Cloud Human Resources 24C What's New, Document ID: docs.oracle.com, Published:
2024-08-27
Section: Document Records Enhancements: "Added Permitted for Mass Download option to limit bulk downloads to specific document types."
Oracle Global Human Resources Cloud: Implementing Global Human Resources, Document ID:
docs.oracle.com, Published: 2023-12-12
Section: Document Management: "Details on configuring document types for mass operations."