1z0-1118-23 Sample Questions Answers

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 operations that are disabled during the scheduled incremental data refresh are ad hoc data refresh for functional areas and semantic model extensions. You cannot perform an ad hoc data refresh for a functional area while a scheduled data load is ongoing, as this may cause conflicts or errors in the data pipeline3. You also cannot perform semantic model extensions while a scheduled data load is ongoing, as this may cause inconsistencies or corruption in the semantic model1. FAW subject areas and decks are not disabled during the refresh, but they may show outdated or incomplete data until the refresh is completed. 

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 prerequisite for creating a data pipeline for any functional area is setting up the pipeline parameters. The pipeline parameters define the global settings for the data pipeline, such as the source application URL, credentials, notification email, incremental refresh frequency, and retention period4. Configuring single sign-on and completing data security assignments are not prerequisites for creating a data pipeline, but they are recommended for securing access to FAW and Fusion Applications5

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 highly recommended best practice is to activate your new UCC subscription into your Oracle Fusion Cloud Applications account followed by activating your Oracle Fusion Analytics Warehouse subscription into the same Oracle Cloud account as your Oracle Fusion Cloud Applications12

 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.

The purpose of the system groups (like FAW Licensed ERP Authors and FAW Functional Administrator) in the FAW Security framework is to grant a user access to FAW based on the system groups to which they are assigned. System groups are predefined groups that specify the user’s system permissions, such as whether they can consume, author, or administer content for a specific module5. System groups do not map duty and data roles or define job-specific roles for users. References: 5

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.

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

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 option that is available in FAW for synchronizing users and job roles between FAW and Fusion Applications is to implement SSO and synchronization of users and job roles between FAW and Fusion Applications, before provisioning the FAW instance. This will allow you to avoid creating Fusion Applications users and their assigned job roles in FAW, as they will be automatically synchronized from Fusion Applications4. You cannot use the FAW console security option or the Bulk Load option in FAW to do the synchronization.