Share Latest Sep-2025 1z0-1046-24Test Practice Test Questions, Exam Dumps
Positive Aspects of Valid Dumps 1z0-1046-24 Exam Dumps!
Oracle 1z0-1046-24 Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
NEW QUESTION # 27
A manager returned from the U.S. Subsidiary to their source location, the U.K. Subsidiary, after a period of three months. What should a Human Resources representative do to reinstate the manager's records in the source legal employer?
- A. Deploy a Descriptive Flexfield to capture the return date. Update this segment with the actual return date to reinstate the record.
- B. Entering the return date will automatically reinstate the record on the return date.
- C. Initiate the End Global Temporary Assignment action and specify a return date. The global temporary assignment is terminated and the assignments in the source legal employer are reinstated automatically on the return date.
- D. Create another assignment with the return date as the effective date.
Answer: C
Explanation:
Full Detailed in Depth Explanation:
For temporary assignments across legal employers (e.g., U.S. to U.K. Subsidiary), Oracle HCM Cloud provides the Global Temporary Assignment feature.
Option D ("Initiate the End Global Temporary Assignment action and specify a return date. The global temporary assignment is terminated and the assignments in the source legal employer are reinstated automatically on the return date") is correct. When a manager returns from a temporary assignment, the HR representative uses the "End Global Temporary Assignment" action, specifying the return date. This automatically terminates the temporary assignment and reinstates the original assignments in the source legal employer (U.K. Subsidiary), as per the "Using Global Human Resources" guide.
* Option A (Descriptive Flexfield) is a custom workaround, not a standard process.
* Option B is incorrect; entering a date alone doesn't trigger reinstatement.
* Option C (new assignment) bypasses the temporary assignment framework.
NEW QUESTION # 28
Which two statements are true about Action and Action Reasons? (Choose two.)
- A. It is mandatory to associate Actions with Action Reasons.
- B. Terminations predictive analytics uses Actions and Reasons data to identify whether a termination is voluntary or involuntary.
- C. The history of effective date changes can be tracked well by using the Actions framework.
- D. There is always a one-to-one relationship between Action Type and Action.
Answer: B,C
Explanation:
Full Detailed in Depth Explanation:
Actions and Action Reasons in Oracle HCM Cloud categorize and explain employment events (e.g., hires, terminations), supporting tracking and analytics.
Option A ("Terminations predictive analytics uses Actions and Reasons data to identify whether a termination is voluntary or involuntary"): True. Oracle Workforce Predictions leverages Actions (e.g., Termination) and Action Reasons (e.g., Resignation vs. Layoff) to classify terminations, as detailed in the "Using Workforce Predictions" guide.
Option B ("The history of effective date changes can be tracked well by using the Actions framework"): True.
The Actions framework logs changes (e.g., promotions, transfers) with effective dates, providing a clear audit trail, per the "Implementing Global Human Resources" guide.
Option C ("It is mandatory to associate Actions with Action Reasons"): False. Action Reasons are optional; an Action (e.g., Termination) can be recorded without a reason.
Option D ("There is always a one-to-one relationship between Action Type and Action"): False. Action Types (e.g., Termination) can have multiple Actions (e.g., Voluntary Termination, Involuntary Termination).
NEW QUESTION # 29
Your customer has decided to use Position Management for at least a portion of their workforce due to the Position Synchronization functionality, which will be beneficial in managing their workforce.
Which are three advantages of using Position Synchronization?
- A. The customer can configure which assignment attributes to synchronize from the position.
- B. For synchronized attributes, any position update will automatically be pushed to the incumbents' assignments.
- C. Synchronized attributes will be displayed as read-only in the assignment to ensure the position as the only source of truth.
- D. If you use Position Synchronization, Manager Self Service cannot be used.
Answer: A,B,C
Explanation:
Position Synchronization in Oracle Global Human Resources Cloud allows assignments to inherit values from associated positions, streamlining workforce management by ensuring consistency between position definitions and employee assignments. The question asks for three advantages of using Position Synchronization, given that the customer has chosen Position Management for this functionality. The provided web results offer detailed insights into how Position Synchronization operates, which are leveraged here to validate the answer.
* Option A: The customer can configure which assignment attributes to synchronize from the position.This is a correct answer. Position Synchronization allows customers to select specific attributes (e.g., job, department, location, manager) to synchronize from the position to the assignment.
This configurability is set at the enterprise or legal entity level using tasks likeManage Enterprise HCM InformationorManage Legal Entity HCM Information. For example, a customer might choose to synchronize the job and manager but not the location, tailoring the synchronization to their needs. Oracle documentation confirms that users can specify which attributes are inherited, providing flexibility in workforce management.
* Option B: For synchronized attributes, any position update will automatically be pushed to the incumbents' assignments.This is a correct answer. When Position Synchronization is enabled, changes to synchronized attributes in a position (e.g., updating a position's department) are automatically reflected in all active assignments linked to that position. This automation reduces manual updates and ensures consistency across incumbents' assignments. TheSynchronize Person Assignments from Positionprocess may be required for retroactive changes, but for active assignments, updates are typically automatic for synchronized attributes. Oracle documentation highlights that synchronized attributes inherit changes, streamlining maintenance.
* Option C: Synchronized attributes will be displayed as read-only in the assignment to ensure the position as the only source of truth.This is a correct answer. To maintain data integrity, synchronized attributes in an assignment are displayed as read-only, preventing manual edits at the assignment level unless override is explicitly allowed. For instance, if the manager attribute is synchronized, the assignment's manager field cannot be changed directly, ensuring the position remains the single source of truth. Oracle documentation notes that this read-only behavior enforces consistency, though overrides can be configured if needed.
* Option D: If you use Position Synchronization, Manager Self Service cannot be used.This option is incorrect. There is no restriction in Oracle HCM Cloud preventing the use ofManager Self Service when Position Synchronization is enabled. Manager Self Service allows managers to perform actions like viewing team details or initiating transactions, and these functions are compatible with Position Synchronization. Oracle documentation does not mention any such limitation, and Position Synchronization operates independently of self-service capabilities, making this option invalid.
* Why these three advantages?The advantages inA,B, andCdirectly align with the benefits of Position Synchronization:configurability(choosing attributes),automation(automatic updates), anddata integrity(read-only attributes). These features reduce administrative effort, ensure consistency, and maintain a single source of truth, which are critical for effective workforce management. OptionDis a false statement, as Position Synchronization does not restrict Manager Self Service.
References
* Oracle Global Human Resources Cloud: Implementing Global Human Resources, Document ID:
docs.oracle.com, Published: 2023-12-12
* Section: Position Synchronization: "You can select attributes to synchronize, and synchronized attributes are inherited automatically by assignments. Synchronized fields are read-only unless overrides are allowed."
* Oracle Global Human Resources Cloud: Using Global Human Resources, Document ID: docs.
oracle.com, Published: 2024-07-02
* Section: Position Management: "Changes to positions are reflected in assignments for synchronized attributes, ensuring consistency."
* Oracle Fusion Cloud Human Resources 24C What's New, Document ID: docs.oracle.com, Published: 2024-08-27
* Section: Workforce Structures Enhancements: "Position Synchronization improvements for attribute management."
NEW QUESTION # 30
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. Jobs are shared by Sets and Positions are assigned to Business Units
- B. Positions may be added to a specific department and location
- C. Jobs and Positions are shared by Sets
- D. When using positions, the grades that are specified for the job become the default grades for the position
Answer: A,B,D
Explanation:
Full Detailed In-Depth 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.
NEW QUESTION # 31
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. Worker Number at the Enterprise Level is set to Manual.
- B. Person Number at the Enterprise Level is set to Automatic after final save.
- C. Person Number at the Enterprise Level is set to Manual.
- D. Person Number at the Enterprise Level is set to Automatic before submission.
Answer: B
Explanation:
Full Detailed In-Depth Explanation:
In Oracle Global Human Resources Cloud, the Person Number generation method is configured via "Manage Enterprise HCM Information." Options include Manual, Automatic before submission, or Automatic after final save. The behavior described-showing "Generated Automatically" with no number on the Review page-indicates the number is assigned post-submission.
Option A: "Automatic before submission" generates the person number immediately upon initiating the hire process, visible before review. This doesn't match the scenario.
Option B: "Worker Number" is distinct from Person Number and irrelevant here. Manual setting would require user input, not "Generated Automatically." Option C: Correct. "Automatic after final save" delays person number generation until the transaction is fully submitted and saved, explaining why it's not visible on the Review page but marked as automatic.
Option D: Manual requires the user to enter a number, contradicting the "Generated Automatically" indication.
The correct answer isC, as detailed in "Implementing Global Human Resources" under Person Number setup.
NEW QUESTION # 32
An employee starts employment with her company in France next month. She was employed by the enterprise in the United States for several years but resigned two years ago. Which statement is correct about the person number for the employee?
- A. The employee has a person record with the enterprise, so she will continue with the same person number.
- B. The employee's new person number will be her previous number suffixed by -1.
- C. The employee gets a new person number for her employment in France if the legal employer sequence is used for person number.
- D. The employee continues with her old person number if a global sequence is used for person number.
Answer: C
Explanation:
Full Detailed In-Depth Explanation:
In Oracle Global Human Resources Cloud, the person number is a unique identifier assigned to an individual within the system. The generation of person numbers can be configured at the enterprise or legal employer level using the "Manage Enterprise HCM Information" or "Manage Legal Entity HCM Information" tasks in the Setup and Maintenance work area. Two common methods for generating person numbers are "Global Sequence" (a single sequence across the enterprise) and "Legal Employer Sequence" (a separate sequence for each legal employer).
Option A: If a global sequence is used, the person number is unique across the enterprise, and typically, a rehired employee might retain their old number if their person record remains active and linked. However, since this employee resigned two years ago, her work relationship with the U.S. legal employer ended. When rehired in France under a different legal employer, Oracle HCM does not automatically reuse the old person number unless explicitly configured to recognize prior records across legal employers, which is not the default behavior for rehires in different jurisdictions.
Option B: When the legal employer sequence is used, each legal employer maintains its own sequence for person numbers. Since the employee is starting employment with a new legal employer in France, she will receive a new person number specific to that legal employer's sequence, regardless of her previous employment in the U.S. This is the correct behavior as per Oracle's employment model, where person numbers can differ across legal employers unless a global sequence is enforced and prior records are explicitly linked.
Option C: While the employee has a prior person record with the enterprise, resignation typically ends the active work relationship. When rehired under a different legal employer, a new person number is generated unless the system is configured to reuse the old number (e.g., via global sequence and specific rehire rules).
The default behavior does not assume continuity of the same person number across legal employers after a resignation.
Option D: Oracle HCM does not automatically suffix a previous person number with "-1" or any similar pattern for rehires. Person number generation follows the configured sequence method, not a manual or derived modification of prior numbers.
Thus, the correct answer isB, as the legal employer sequence method generates a new person number for the employee in France. This aligns with the documentation in "Implementing Global Human Resources" (e.g., section on Person Number Generation in the Manage Legal Entity HCM Information task).
NEW QUESTION # 33
As an implementation consultant, you have configured several rules in Transaction Design Studio within the test environment. How do you migrate these changes to your production environment?
- A. Use the Configuration Package capabilities of Functional Setup Manager to export the configurations.
- B. Use the Configuration Package capabilities within the Configuration > Migration work area.
- C. Transaction Design Studio changes can't be migrated from one instance to another. You will need to reconfigure the transactions within your production environment.
- D. Use the Configuration Set Migration tool within the Configuration > Migration work area.
Answer: D
Explanation:
Full Detailed In-Depth Explanation:
In Oracle HCM Cloud, Transaction Design Studio (TDS) configurations (e.g., rules for transactions like Promote or Hire) are migrated between environments using theConfiguration Set Migration tool, accessible via the Configuration > Migration work area. This tool allows you to export TDS rules as a configuration set from the test environment and import them into production, preserving customizations like field visibility or validation rules. The process involves selecting the TDS configurations, exporting them as a .zip file, and importing them into the target instance, ensuring consistency across environments.
Option A (Functional Setup Manager's Configuration Package) is used for broader setup data (e.g., enterprise structures), not TDS-specific rules. Option C misplaces the Configuration Package under the Migration work area, which is incorrect. Option D is false-TDS changes aremigratable. Option B correctly identifies the Configuration Set Migration tool as the method, per Oracle's migration guidelines.
NEW QUESTION # 34
An organization is running a fitness program. They want to identify a Fitness Representative who will be responsible for a group of people in the organization. How should you set this up?
- A. Deploy a Key Flexfield to capture the information.
- B. Define the person's area of responsibility to reflect Fitness Representative.
- C. Create a new job Fitness Representative and associate that to the person.
- D. Deploy a Descriptive Flexfield to capture the information.
Answer: B
Explanation:
Full Detailed in Depth Explanation:
Oracle HCM Cloud allows assigning responsibilities to individuals for specific tasks or groups, such as a Fitness Representative for a fitness program. The setup should leverage existing functionality efficiently.
Option D ("Define the person's area of responsibility to reflect Fitness Representative") is correct. In Oracle HCM, "Areas of Responsibility" (AOR) can be defined via the "Manage Areas of Responsibility" task to assign specific duties (e.g., Fitness Representative) to a person for a group of workers. This is a standard feature for designating responsibilities without requiring new jobs or flexfields, as outlined in the
"Implementing Global Human Resources" guide.
* Option A ("Deploy a Key Flexfield to capture the information") is incorrect. Key Flexfields (KFFs) are used for structured data (e.g., job codes), not responsibilities.
* Option B ("Deploy a Descriptive Flexfield to capture the information") could work for custom attributes but is overkill when AOR is available.
* Option C ("Create a new job Fitness Representative and associate that to the person") is unnecessary; a job defines a role, not a specific responsibility for a program.
NEW QUESTION # 35
Which option represents the basis on which approval routing policies can be defined?
- A. Employee Supervisor Hierarchy, Position Hierarchy, Job Levels, Approval Groups, Organization Hierarchy
- B. Employee Supervisor Hierarchy, Position Hierarchy, Job Levels, Approval Groups
- C. Employee Supervisor Hierarchy, Position Hierarchy, Grades, Approval Groups, Organization Hierarchy
- D. Employee Supervisor Hierarchy, Position Hierarchy, Job Levels, Department Manager
Answer: B
Explanation:
Full Detailed In-Depth Explanation:
Approval routing policies in Oracle HCM Cloud, configured via Transaction Console or BPM Worklist, use specific bases to define approver chains. The documentation lists these as:Employee Supervisor Hierarchy (management chain),Position Hierarchy(position-based reporting),Job Levels(relative to the requester's job level), andApproval Groups(static or dynamic groups). These options provide flexibility to route approvals based on organizational structure or predefined lists, covering most use cases.
Option B includes "Grades," which influence salary, not approvals, and "Organization Hierarchy," which isn't a direct routing basis. Option C adds "Organization Hierarchy," which is redundant with Supervisor Hierarchy. Option D's "Department Manager" isn't a distinct basis-it's part of Supervisor Hierarchy. Option A accurately reflects Oracle's supported routing bases.
NEW QUESTION # 36
As part of a client's configuration requirements, they have indicated that they want to create divisions by Line of Business in HCM Cloud. After creating them, in which two ways can you associate workers with a specific division?
- A. Division is a delivered field on a position. If you are using Positions, when you associate a worker with a position, they will be associated with the division tied to that position.
- B. Division is a delivered field on the worker assignment. Therefore, when a worker is hired, the correct division would be selected by the user entering the information.
- C. You configure and deploy an assignment descriptive flexfield that has a table value set that references the Division object. When you complete a worker's assignment, you select the appropriate division through that flexfield segment.
- D. You have configured an Organization Tree, listing the hierarchy of your Legal Entities, Divisions, Business Units, and Departments. You associate a worker with a department that falls within a division to associate the worker with that division.
Answer: C,D
Explanation:
Full Detailed in Depth Explanation:
Divisions in Oracle HCM Cloud are organizational units often aligned with lines of business. Associating workers with divisions requires leveraging existing structures or custom fields.
Option B ("You configure and deploy an assignment descriptive flexfield that has a table value set that references the Division object"): True. A Descriptive Flexfield (DFF) on the assignment can be configured with a value set linked to the Division object, allowing manual selection during assignment updates, as per the
"Implementing Global Human Resources" guide.
Option D ("You have configured an Organization Tree, listing the hierarchy of your Legal Entities, Divisions, Business Units, and Departments"): True. By associating a worker with a department within a division via the organization hierarchy, the worker is indirectly linked to that division, a standard practice in workforce structures.
Option A ("Division is a delivered field on a position"): False. Position has fields like Department, but Division is not a standard delivered field.
Option C ("Division is a delivered field on the worker assignment"): False. Assignment includes fields like Department, not Division directly.
NEW QUESTION # 37
Which option represents the basis on which approval routing policies can be defined?
- A. Employee Supervisor Hierarchy, Position Hierarchy, Job Levels, Approval Groups, Organization Hierarchy
- B. Employee Supervisor Hierarchy, Position Hierarchy, Job Levels, Approval Groups
- C. Employee Supervisor Hierarchy, Position Hierarchy, Job Levels
- D. Employee Supervisor Hierarchy, Position Hierarchy, Grades, Approval Groups, Organization Hierarchy
Answer: B
Explanation:
Full Detailed in Depth Explanation:
In Oracle Global Human Resources Cloud, approval routing policies determine how transactions (e.g., promotions, transfers) are routed for approval. These policies are configured using the "Manage Approval Transactions" task and rely on specific hierarchies and groups.
Option B ("Employee Supervisor Hierarchy, Position Hierarchy, Job Levels, Approval Groups") is correct.
Oracle HCM Cloud supports the following bases for defining approval rules:
* Employee Supervisor Hierarchy: Routes approvals through the employee's reporting structure.
* Position Hierarchy: Uses the position hierarchy if positions are implemented.
* Job Levels: Routes based on job level differences (e.g., requiring higher-level approval for significant changes).
* Approval Groups: Predefined groups of approvers for specific transactions.
The "Implementing Global Human Resources" guide confirms these as the standard components.Grades and Organization Hierarchy (e.g., Department or Division) are not directly used in approval routing policies, making other options incorrect.
* Option A includes "Grades" and "Organization Hierarchy," which are not standard bases.
* Option C omits "Approval Groups," which is a key component.
* Option D adds "Organization Hierarchy," which is not supported for approval routing.
NEW QUESTION # 38
As an HR Specialist, it is your responsibility to hire employees and enter their base salary information. After you selected a grade and salary basis, and entered the base salary, you expected to see the compa-ratio information display-but it does not. What is the possible cause for the information NOT displaying?
- A. The grade rate and the salary basis are tied to different frequencies.
- B. The grade and the salary basis are tied to different legislative data groups.
- C. The grade rate was not linked to the salary basis.
- D. The grade rate and the salary basis are tied to different legislative data groups.
Answer: C
Explanation:
Full Detailed In-Depth Explanation:
In Oracle Global Human Resources Cloud, the compa-ratio (comparison ratio) measures an employee's salary against the midpoint of a grade rate range. It's displayed in the employment or salary details section when entering a base salary, provided all components are correctly aligned.
* Option A: Incorrect. Grade rates and salary basis don't need to share the same legislative data group (LDG) for compa-ratio calculation; LDGs partition data but don't directly affect this display unless misconfigured at a higher level.
* Option B: Incorrect. The grade itself isn't tied to an LDG; it's the grade rate that matters. This option misattributes the relationship.
* Option C: Incorrect. While frequency (e.g., monthly vs. annual) must align for accurate salary calculations, compa-ratio is normalized and should still display if the grade rate and salary basis are linked, even with frequency differences (assuming conversion is handled).
* Option D: Correct. The compa-ratio requires a grade rate (defining min, mid, max values) to be associated with the salary basis used in the employee's record. If the grade rate isn't linked to the salary basis (via "Manage Salary Basis" or "Manage Grade Rates"), the system lacks the reference range to compute and display the compa-ratio. This is a common setup oversight during implementation.
The correct answer isD, as detailed in "Using Global Human Resources" on salary management and grade rate integration.
NEW QUESTION # 39
Which three options are true regarding Grade Ladders?
- A. Two types of Grade Ladders are available.
- B. A Grade Ladder cannot be created with a combination of both grades and grades with steps.
- C. Grade Ladders are used to group grades or grades with steps.
- D. A Grade Ladder can be created with a combination of both grades and grades with steps.
Answer: A,C,D
Explanation:
Full Detailed In-Depth Explanation:
In Oracle Global Human Resources Cloud, Grade Ladders organize grades (flat pay levels) or grades with steps (progression points within a grade) to manage compensation structures.
Option A: Correct. Grade Ladders group grades (without steps) or grades with steps, providing a framework for salary progression or rate assignment, as defined in the "Manage Grade Ladders" task.
Option B: Incorrect. Oracle allows flexibility; a Grade Ladder can mix grades without steps and grades with steps, though it's less common and depends on configuration.
Option C: Correct. A Grade Ladder can include both types (grades and grades with steps), offering versatility in structuring pay scales, as supported by the system's grade ladder setup options.
Option D: Correct. Two types of Grade Ladders exist:
Grade Ladder with Grades: For flat grades without steps.
Grade Ladder with Steps: For grades with progression steps.
This is explicitly outlined in Oracle documentation.
The correct answers are A, C, and D, per "Implementing Global Human Resources" on grade structures.
NEW QUESTION # 40
Your customer wants to know how many employees are leaving the organization on their own. What is the correct sequence of steps that you need to perform to meet this requirement?
- A. Create a new action type, create a new action reason and use it during termination
- B. Create a new action reason, associate the action reason with a new or existing action, use that action and action reason during termination
- C. Create a new action reason and associate it with the available action type, use it during termination
- D. Create a new action, create a new reason and use it during termination
- E. Create a new action type, create a new action, create a new action reason and use it during termination
Answer: B
Explanation:
Full Detailed In-Depth Explanation:
To track voluntary terminations in Oracle Global Human Resources Cloud, the "Managing Workforce Records" guide advises:
* Create a new action reason: Define a specific reason (e.g., "Voluntary Resignation").
* Associate it with a new or existing action: Link it to an existing Action (e.g., "Termination") or create a new one (e.g., "Voluntary Termination").
NEW QUESTION # 41
You are an HR specialist and want to add new values to a lookup. You have access to the specific work area, but are unable to perform the activity. Identify the correct statement about this.
- A. Oracle applications contain certain predefined system lookups that are locked for editing.
- B. You can access the task for profile options from the Setup and Maintenance menu.
- C. The system administrator must enable the lookup before it is modified in the work area.
- D. You cannot add new lookup codes and meanings to the existing lookup types.
- E. You can create new lookup types but cannot modify the existing ones.
Answer: A
Explanation:
Full Detailed In-Depth Explanation:
In Oracle Global Human Resources Cloud, lookups are managed via the "Manage Common Lookups" or
"Manage Standard Lookups" tasks in the Setup and Maintenance work area. Lookupsprovide drop-down values (codes and meanings) for fields, and their editability depends on their type and configuration.
* Option A: Incorrect. You can add new lookup codes and meanings to many existing lookup types, provided they are not system-locked or restricted by security.
* Option B: Correct. Oracle includes predefined system lookups (e.g., seeded values for core fields like Action Types or Employment Status) that are locked for editing to maintain application integrity. If the lookup you're trying to modify is one of these, you'll be unable to add values, even with access to the work area, due to system restrictions.
* Option C: Incorrect. Profile options are unrelated to lookups; they control application behavior, not value lists, and don't explain the inability to edit.
* Option D: Incorrect. You can modify existing lookup types (if not system-locked) and create new ones, depending on permissions and lookup status.
* Option E: Incorrect. There's no specific "enable" step by a system administrator for lookups; editability is determined by the lookup's system status and user privileges.
The correct answer isB, as per "Implementing Global Human Resources" on lookup management, where system lookups are noted as non-editable.
NEW QUESTION # 42
......
Practice LATEST 1z0-1046-24 Exam Updated 160 Questions: https://www.troytecdumps.com/1z0-1046-24-troytec-exam-dumps.html
First Attempt Guaranteed Success in 1z0-1046-24 Exam: https://drive.google.com/open?id=1aGxhPYYDC0MRzomCfadcZKGImi44lNNg