Free Oracle 1z0-1118-23 Practice Exam with Questions & Answers | Set: 2

The step that would be required for the data pipeline to run without any issues after your source Fusion Cloud Application instance has been refreshed with data from another environment is to update the applicable users credentials, if the passwords differ between environments. You need to ensure that the FAWService user and any other users that are used for data extraction have valid credentials in both environments8. You do not need to update the source application URL or the notification email of the FAW instance for this purpose

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

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.

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

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.