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

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.

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

 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

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

The way that you would secure your Fact table using data filters from different dimensions is to use functional groups to combine the data filters using the OR and AND operators. Functional groups are logical groups of dimensions that can be used to apply data filters on a Fact table. You can use functional groups to specify complex filter criteria that involve multiple dimensions and operators3. You do not need to create multi-table data sets in OAC or accept that this scenario is not supported.

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

 You can extend the dimension that you created using Data Augmentation by using Semantic Model Extensions. You need to create a branch and add a step of “Extend a Dimension”. Youcan then select the dimension that you want to extend and add a new attribute data source from another table or view

To create a multi-user development environment for customizing the semantic model, each developer has to create their own branch and perform all modifications inside the branch. The branches can be merged with the main branch after testing and validation6. OAC tools are not required for this purpose.

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

FAW provides two features to customize and extend the semantic model: Semantic Model Extensions and Data Augmentation. Semantic Model Extensions allow you to modify the existing dimensions, facts, and subject areas, as well as create new ones from existing data sources. Data Augmentation allows you to create new dimensions, facts, and subject areas from custom data sources that are not part of the FAW data pipelin

The Reporting Configuration parameters are used to define how the data is displayed in the FAW user interface. They include settings such as currency, date format, decimal separator, number of decimals, and default dashboard. These parameters affect the presentation layer of the FAW semantic model and can be changed at any time without affecting the data pipeline or the data warehouse.

Verified References: Oracle Fusion HCM Analytics, page 9.

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

 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. 

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.