A financial organization needs to refresh General Ledger and Purchase Order data every 4 hours during quarter-end closing to ensure analysts have intraday transactional visibility. The administrator is setting up the Frequent Data Refresh schedule in the Oracle Fusion Data Intelligence Console.
Which TWO conditions or prerequisites must be satisfied to successfully configure and run this intraday frequent data refresh?

• A. The Frequent Refresh feature must be enabled under Pipeline Features on the Enable Features page prior to scheduling.
• B. The incremental pipeline schedule for the applicable functional area must be configured for a daily frequency.
• C. The Virus Scanner console task must be configured to scan intraday staging tables prior to ingestion.
• D. The administrator must execute a manual semantic model update after every 4-hour refresh cycle.
• E. A private endpoint must be deployed in OCI to bypass the daily Autonomous Data Warehouse maintenance window.

An administrator is setting up data validation using basic credentials for a dedicated validation user named MyFAWValidationUser in an environment where OAuth authentication is not configured. On which Console tab under Application Administration must these user credentials be entered and maintained?

• A. System Settings
• B. Source Credentials
• C. Pipeline Parameters
• D. Object Permissions

Which statement is true regarding user and group management in Oracle Fusion Data Intelligence?

• A. Deleting a group in the FDI Console permanently removes the corresponding group from Oracle Cloud Infrastructure Identity and Access Management.
• B. Assigning an FDI application role to an identity domain group automatically grants all members of that group the permissions associated with the role.
• C. Application roles must be assigned individually to each user and cannot be mapped to identity domain groups.
• D. Users and groups are created directly within the FDI Console, bypassing the Oracle Cloud Infrastructure Identity Domain.

You have completed a direct promotion of modified User Extensions and custom subject area joins from your non-production environment to Production using the Promote Objects console task.
What is the published status of these semantic model customizations in the Production environment upon completion?

• A. The promoted customizations are held in staging until the next scheduled quarterly release update completes.
• B. The promoted customizations overwrite only the physical layer while leaving presentation subject areas hidden.
• C. The promoted customizations are stored as uncommitted draft steps in Production requiring manual publishing in Semantic Model Extensions.
• D. The promoted customizations are automatically applied and published directly to the Production semantic model.