In Oracle Planning 2024, predefined roles in Cloud EPM determine user permissions. The requirement is for a role that allows a Planning user to create and administer Planning or Planning Modules and service components, as well as grant permissions to other users. Among the options:
* A. System Administrator: Incorrect. This role exists in some Oracle systems but is not a Cloud EPM predefined role specific to Planning. It's too broad and not aligned with EPM terminology.
* B. Approvals Administrator: Incorrect. This role manages approval processes (e.g., workflows) but does not include creating/administering applications or granting permissions beyond approvals.
* C. Identity Role Administrator: Incorrect. While this role manages identity and access (e.g., assigning roles), it does not allow creating or administering Planning applications or service components.
* D. Service Administrator: Correct. The Service Administrator role in Cloud EPM allows users to create and manage Planning applications, configure modules and service components (e.g., forms, rules), and assign permissions to other users via access control.
The Service Administrator role is the highest-level predefined role in Oracle EPM Cloud for Planning, encompassing application management and user permission assignments, making it the correct choice.
References:
Oracle Planning 2024 Implementation Study Guide: "Predefined Roles in Cloud EPM" (docs.oracle.com, Published 2024-08-25).
Oracle EPM Cloud Documentation: "Managing Users and Roles" (docs.oracle.com, Published 2023-10-30, updated for 2024).

In Oracle Planning 2024's Workforce module, certain configuration tasks are mandatory to enable basic functionality, while others are optional depending on the organization's needs. The task that is not mandatory is:
* A. Employee Type: Incorrect. Defining Employee Type (e.g., full-time, part-time) is mandatory because it establishes the categories of employees to be planned, forming the foundation of workforce data.
* B. Planning and Forecast Preparation: Incorrect. This task is mandatory as it sets up the planning periods, scenarios, and versions, which are essential for Workforce to function within the broader Planning application.
* C. Benefits and Taxes: Correct. Configuring Benefits and Taxes is optional. While Workforce provides predefined options to calculate benefits (e.g., health insurance) and taxes (e.g., payroll taxes), organizations can choose not to configure these if they do not need detailed compensation planning beyond salaries.
* D. Workforce Assumptions: Incorrect. Workforce Assumptions (e.g., hiring rates, salary increases) are mandatory to drive calculations and populate employee data over time.
The Oracle documentation specifies that while Benefits and Taxes enhance Workforce planning, they are not required for core functionality, making C the non-mandatory task.
References:
Oracle Planning 2024 Implementation Study Guide: "Configuring Workforce Module" (docs.oracle.com, Published 2024-10-01).
Oracle EPM Cloud Documentation: "Workforce Configuration Tasks" (docs.oracle.com, Published 2023-11-
20, updated for 2024).

Before an EPM (Enterprise Performance Management) administrator can import a Machine Learning (ML) model into Oracle Planning, a prerequisite task must be completed by data scientists. According to Oracle's
"Bring Your Own ML" feature in the Planning application, the process begins with data scientists gathering historical data related to a business problem, training an ML algorithm, and generating a Predictive Model Markup Language (PMML) file using a third-party data science tool or Oracle Data Science Cloud. This PMML file represents a fully trained ML model that can then be imported into the Planning application by an EPM administrator.
Option A is correct because it aligns with this prerequisite step: the ML model must be pretrained and saved as a PMML file before the import process can begin. Option B is incorrect because Groovy rules are not created by data scientists to evaluate historical data; instead, these rules are automatically generated by the Planning application during the import process to integrate the ML model with the application. Option C is also incorrect, as EPM administrators do not generate PMML files by creating data models and pushing data- instead, they import an existing PMML file. Finally, Option D is incorrect because while EPM administrators may create data maps and Groovy rules as part of the deployment process, this occurs after the PMML file is imported, not before.
The Oracle Planning 2024 Implementation documentation emphasizes that the "Bring Your Own ML" functionality relies on importing a prebuilt PMML file, making the data scientists' role in building and training the model a mandatory first step.
References:
Oracle Planning 2024 Implementation Study Guide: "Bring Your Own ML: About Machine Learning Model Import" (docs.oracle.com, Published 2024-09-04).
Oracle EPM Cloud Documentation: "Importing ML Models" (docs.oracle.com, Published 2022-06-17, updated for 2024).