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

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.

The way that you can address your requirements in FAW when FAW does not move and replicate your entire security implementation from Fusion Applications is to evaluate your security requirements and utilize security customization features in FAW to meet your needs. FAW provides various security customization features, such as custom data roles, custom duty roles, custom security configurations, and functional groups, that allow you to define advanced data security and object security4. You do not need to set up SSO between FAW and Fusion Applications or open a support ticket for this purpose.

Data Augmentation is a feature in FAW that supports both data movement and semantic model extensibility to provide missing data elements. Data Augmentation allows you to extract data from additional data sources that are not part of the FAW data pipeline and load them into ADW. You can then use the data to customize the semantic model and create new dimensions, facts, and subject areas2

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

 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 security privilege that is required by the user to activate UCC and FAW in your Oracle Cloud account is to be a Cloud Account Administrator in the Oracle Cloud account. The Cloud Account Administrator is responsible for activating UCC and FAW subscriptions, managing users and roles, configuring security settings, monitoring service usage, and performing other administrative tasks6. The user does not need to be a Business Administrator or have no special security privileges to activate UCC and FAW in the Oracle Cloud account.

Semantic Model Extensions provide various capabilities to customize the semantic model, such as adding a new dimension, adding a new fact, extending a dimension, extending a fact, creating a new subject area, reorganizing a subject area, and adding additional data sources5. Creating a union between two tables is not supported by Semantic Model Extensions.

The FAW Security framework allows a flexible and extensible mapping of Security Content to Data Roles. A Security Content is a predefined attribute that defines the boundaries of data access for a given subject area, such as Business Unit, Country, Department, Job Family, Legal Entity, and Worker Type. A Data Role is a custom role that grants access to specific subsets of data in the data warehouse based on the Security Content. A Security Content can be mapped to multiple Data Roles, and a Data Role can have multiple Security Content associated with it. For example, a Security Content of Country = US can be mapped to a Data Role of US HR Manager, and a Data Role of US HR Manager can have multiple Security Content such as Country = US, Business Unit = Sales, and Department = Marketing.

Verified References: Reference for Fusion HCM Analytics, page 9-10.

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

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