1z0-1118-23 Oracle Cloud Fusion Analytics Warehouse 2023 Implementation Professional Questions and Answers

Oracle Fusion Analytics Warehouse is built on top of Oracle Analytics Cloud and Oracle Autonomous Data Warehouse. This packaged service starts with Oracle Fusion Cloud Applications, and you can deploy rapidly, personalize, and extend it1

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 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

The way that the Subject Areas are secured in FAW is by using duty roles. Duty roles define the functional security for a user, such as which tasks they can perform or which objects they can view. Duty roles also determine which subject areas a user can access based on their job functions1. There is a need to secure Subject Areas as the data security alone does not provide the necessary security access. Unlike Fusion Applications, the Subject Areas are not open to any FAW-licensed user, but only to those who have the appropriate duty roles

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 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 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

 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. 

You can create multiple branches to customize the semantic model. You use a branch or version to publish your changes to the model. You can apply the model from the branch to a local service instance for testing. When the changes are correct, you can merge that branch with the main branch3

The smallest interval of incremental data load to the FAW data warehouse is daily. You can configure the incremental refresh frequency for each functional area in the pipeline settings. The minimum frequency that you can set is daily, which means that the data pipeline will run once every 24 hours and bring in the latest data from your Fusion Applications4. You cannot set the frequency to be hourly or weekly, as these are not supported by FAW.

To create custom data security to meet your data security requirements, you need a combination of steps in Security Console and the Security Configurations in the Semantic Model Extensions available at the FAW Console. The Security Console allows you to create custom data roles and assign them to users or groups5. The Security Configurations allow you to define custom security filters and apply them to dimensions, facts, or subject areas6. You do not need to use only the Security Configurations or modify the Data Security Assignment file for this purpose. 

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.

Based on a standard subscription, you can create two instances of Oracle Fusion Analytics Warehouse: one for development/testing, and a second for production use. You can use the development/testing instance to test new features or customizations before deploying them to the production instance3