1z0-1118-23 Practice Exam Questions with Answers Oracle Cloud Fusion Analytics Warehouse 2023 Implementation Professional Certification

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. 

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

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.

 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. 

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.

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

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 perform data validation from the FAW console, you need to ensure that you have the same data security privileges in the FAW instance and the Oracle Transactional Business Intelligence (OTBI) instance. This will allow you to compare the metrics between the two instances and verify their accuracy1. You do not need to have access to all data in the FAW instance or have the administrator privilege in the OTBI instance to perform data validation. 

The DFFs and their attributes must be BI-enabled in order to be extracted by the FAW data pipeline and loaded into the data warehouse. BI-enabling a DFF means that it is exposed as a column in a view object that is part of a subject area in Oracle Transactional Business Intelligence (OTBI). This allows FAW to access the DFF data through OTBI web services.

Verified References: Use Descriptive Flexfields, section 23.1; About Flexfields, section “Use Flexfields in Your Data Model”.

 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

To perform data validation from the FAW console, you need to ensure that you have the same data security privileges in the FAW instance and the Oracle Transactional Business Intelligence (OTBI) instance. This will allow you to compare the metrics between the two instances and verify their accuracy2. You do not need to have access to all data in the FAW instance or have the administrator privilege in the OTBI instance to perform data validation.