Oracle Updated 1z0-1177-26 Exam Questions and Answers by norah

The intended answer is B and D , but the terminology is version-specific. Oracle SQL Developer historically used the connection type Cloud PDB for wallet-based Autonomous Database connections. The user selected Cloud PDB, browsed to the downloaded client-credentials ZIP file, supplied the wallet/keystore password, selected the database service, tested the connection, and saved it.

Oracle subsequently renamed this connection type Cloud Wallet . Current Oracle documentation specifies Cloud Wallet, the client-credentials configuration file, database user credentials, and an appropriate service name. Oracle explicitly notes that Cloud PDB is the older name , including in SQL Developer 18.2-era workflows. Therefore, option B remains the intended examination choice because Cloud Wallet isn't offered among the options.

The service list represents database service names such as high, medium, or low service configurations; it doesn't represent OCI compartments. ODBC and Basic connections aren't the wallet-based configuration described.

Accordingly, B and D match the historical workflow reflected by the question, while candidates should recognize that Cloud Wallet is the current SQL Developer terminology .

Reference Topic: Connecting to Data Sources — SQL Developer Connections to Autonomous Data Warehouse

===============

Report Scheduling provides the required automation. Oracle Analytics Publisher's Schedule Report Job interface lets an administrator specify a report, configure its output, select one or more delivery destinations, and define exactly when or how frequently the job executes.

For this scenario, the administrator would configure a recurring schedule for Monday at 6:00 AM, select PDF as the output format, and configure Email as the delivery destination with the management recipients. Oracle's official scheduling tutorial demonstrates the same fundamental workflow: create a report job, select PDF output, configure an email destination, and define the execution schedule.

Runtime Configuration controls system-level processing and output properties; it isn't the scheduler. Template Builder is used to design RTF report templates, while an SQL Data Set retrieves report data and doesn't determine when the report executes.

The uploaded source also identifies Report Scheduling as the mechanism that automates report execution at specified intervals and supports email and other delivery channels. Therefore, the correct answer is B. Report Scheduling .

Reference Topic: Managing Report Scheduling, Data Sources, Administration, and Translations — Report Jobs and Scheduling

===============

A “Subject Area not found” condition points first to the analytical metadata layer rather than to dashboard rendering. Analyses reference subject areas exposed by the deployed semantic model. If the expected semantic model wasn't migrated or deployed correctly, if the relevant presentation subject area is missing, or if its name/mapping no longer matches what the analysis references, the dashboard itself can open while individual analyses fail.

Oracle's OAC migration workflow explicitly treats the Data Model and Subject Areas as snapshot components. During certain migration procedures, administrators may deliberately exclude these components from snapshot restoration and separately upload an updated semantic model. This makes verification of the deployed semantic model and its exposed subject areas a critical production-validation step.

Browser compatibility does not create or remove subject-area metadata. Email configuration applies to delivery, and Publisher Runtime Configuration controls report-processing behavior rather than Classic Analysis subject-area resolution.

Therefore, the administrator should first verify that the expected semantic model is deployed and the referenced subject areas and mappings exist correctly , making B the technically supported response.

Reference Topic: Connecting to Data Sources and Migrating Artifacts — Semantic Model and Subject Area Migration

Catalog Object Permissions provide the required authorization control for shared Oracle Analytics content. Dashboards, analyses, folders, and related catalog objects can be assigned permissions that determine which users or application roles can read, modify, delete, or otherwise manage them. For this scenario, the administrator can grant the Finance application role appropriate modification privileges while granting other authorized consumers read-only access.

Oracle recommends assigning access through roles rather than individual users wherever possible. This simplifies administration because users inherit the catalog permissions associated with their application-role membership. Shared-folder permissions can also be used so that contained objects inherit a consistent security configuration.

A Dashboard Prompt controls filtering and runtime input, not modification rights. Data Gateway provides connectivity to remote or on-premises sources. Query Cache improves analytical query performance but has no role in dashboard authorization.

The uploaded source identifies Catalog Object Permissions for this scenario, and Oracle documentation confirms that shared analytics content can be secured using permissions assigned to users and roles.

Reference Topic: Managing Administration, Security, and Performance — Catalog Security and Object Permissions

===============