Oracle 1z0-1118-23 Oracle Cloud Fusion Analytics Warehouse 2023 Implementation Professional Exam Practice Test

 It is possible to set up SSO between Fusion Applications and FAW in this case, where you have already set up SSO for Fusion Applications between Active Directory and Fusion Applications. The configuration process to set up SSO between Fusion Applications and FAW stays the same, regardless of whether you use Active Directory or another IdP as your primary authentication source5. This configuration is supported and not complex or discouraged by Oracle. 

LBAC (Location-Based Access Control) is a feature that restricts access to Fusion Applications based on IP addresses or ranges of IP addresses. If LBAC is enabled on your Fusion pod, you need to identify a user who will be used by FAW to connect to Fusion Applications using password-based authentication. This user must have access from All IP Addresses in order to allow FAW to extract data from any location.

Verified References: Securing Oracle Fusion Applications REST APIs with Location Based Access Control (LBAC), section “LBAC Configuration”.

The benefit of using System Provided source tables for extraction from Fusion Applications is that they are prevalidated by Oracle Fusion Analytics Warehouse. As part of that validation, Oracle helps ensure the success of processing and mitigates performance impact7. System Provided source tables are a subset of Business Intelligence view objects that are available for Data Augmentation8. You do not get complete access to all transaction tables or real-time sync with System Provided source tables.

To test your customization, you need to publish the branch that contains your customization. This will apply the changes to the model and make them available in the subject areas. You can then use OAC console to create and view reports based on your customized model3

To move external data to ADW that comes with FAW, you can use Manage Connections to create a connection to available sources, such as Oracle Database, Oracle Autonomous Database, Oracle Object Storage, Oracle Applications Cloud, and others4. Data Augmentation can then be used against these connections to bring data into ADW5. You can also use OAC Data Replication feature to replicate data from other sources into ADW6

You cannot recover a terminated instance of FAW from the OCI console. When you terminate an instance, all the resources associated with it are permanently deleted, including the OAC instance, the ADW instance, and the data warehouse. You will have to re-create your instance and restore it from a snapshot if you have one7. You cannot recover a terminated instance by opening a Service Request (SR) with Oracle support or by clicking a button from the OCI console. 

The typical use case of the Promote Objects feature is to move your customization from one environment to another, such as from development to production. The Promote Objects feature allows you to export and import your customizations of the semantic model, security configurations, and KPIs between different instances of FAW4. The Promote Objects feature is not used to check the validity of your customization or to replicate one instance to another.

The steps that you would take to override the default data security for specific users are to create a custom data role and set up data filters that specify the values for specific dimensions. A custom data role allows you to define custom data security filters and apply them to dimensions, facts, or subject areas. You can then assign the custom data role to the users who need to have different data access than the default2. You do not need to create a custom duty role or create reports with filters to override the default data security.

To scale up your associated Oracle Autonomous Data Warehouse (ADW) and OAC as part of your FAW customization, you need an OCI Administrator with access to OCI pages for OAC and ADW instances. The OCI Administrator can use the OCI Console or APIs to scale up or down the compute resources (CPU cores) or storage resources (terabytes) for both ADW and OAC instances

The setup sequence for implementing SSO to access FAW is to set up SSO before proceeding with the FAW instance creation. You need to configure SSO between your identity provider (IdP) and Fusion Applications before you provision your FAW instance. This will enable SSO and synchronization of users and job roles between Fusion Applications and FAW4. You cannot create the FAW instance first or ignore the setup sequence for implementing SSO

To address your specific security business requirements within the FAW Application, you can use the security customization in FAW for both data security and object security. Data security allows you to restrict access to data based on various attributes, such as business unit, legal entity, department, or any other filter criteria7. Object security allows you to restrict access to objects, such as subject areas, facts, dimensions, KPIs, dashboards, or reports based on user roles or groups8. You do not need to address those requirements in Fusion Applications or rely on only the out-of-the-box security model.

 The best practice for upgrading a FAW instance to the latest version is to schedule the upgrade through the FAW console. You can use the Upgrade option on the Console page to select the available version and schedule a date and time for the upgrade. You can also view the status and history of your upgrades on the same page1. You do not need to open an SR with Oracle or wait until Oracle upgrades the instance for this purpose.

 The way to ensure that your changes to the global pipeline parameters are deployed and data is consistent is to wait for the next incremental upload. Changes to the global pipeline parameters take effect at the next incremental upload, which is scheduled based on the frequency that you set in the parameters9. You do not need to reset the data warehouse or activate the functional areas for this purpose. Changes to the global pipeline parameters do not take effect immediately.

You can use FAW Semantic Model Extensions to customize the semantic model and join the Fusion Applications data with external data. You can extend ready-to-use dimensions with additional attributes from another data source, add a fact to an existing subject area, and reorganize the ready-to-use subject areas to create a new subject area to name a few

The type of Application Role that is used to secure access to the Subject Area is the Data Role. The Data Role defines the data security context for a user, such as which business units, legal entities, or departments they can access2. The Duty Role defines the functional security for a user, such as which tasks they can perform or which objects they can view3. Any of the Application Role types cannot be used to secure access to the Subject Area, as they have different purposes. 

 You can create a dimension using Semantic Model Extensions and join it with any Fact table, whether it is a custom Fact table or an out-of-the-box Fact table. You can also join multiple dimensions with a single Fact table3