Oracle 1z0-1177-26 Practice Test Questions Answers

The Autonomous Data Warehouse wallet is obtained from the Oracle Cloud Infrastructure Console , not generated by SQL Developer. The administrator or authorized user first navigates to the appropriate compartment and selects the Autonomous Database instance. From the database details, the Database Connection function provides access to client credentials.

Oracle's current procedure then requires selecting the appropriate wallet type and choosing Download Wallet . A password is supplied and confirmed to protect the downloaded wallet package. The resulting ZIP file contains the secure client credentials and network configuration needed by supported database clients.

SQL Developer uses the wallet only after it has been downloaded. Selecting a service name therefore belongs to the subsequent database-connection process rather than wallet retrieval. Running SQL Developer doesn't need to precede access to the OCI database details, and an independently downloaded JDBC driver isn't a prerequisite for obtaining the wallet.

The terminology in option D uses the older DB Connection label, while current OCI documentation generally uses Database connection , but the workflow remains the same. Therefore, B and D are correct.

Reference Topic: Connecting to Data Sources — Autonomous Data Warehouse Client Credentials and Wallets

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

The intended administrative function is Manage Sessions . Oracle documents session monitoring as the mechanism for viewing the total number of active sessions and detailed information about currently signed-in users. Available details include the user identifier, browser information, login time, last-access time, and associated query activity.

In current Oracle Analytics Cloud interfaces, this functionality is surfaced through Console → Sessions and Query Logs , where the Sessions section displays the total number of sessions and user details. Earlier and related Oracle Analytics interfaces expose the same capability as Administration → Manage Sessions . Since that is the terminology supplied by the answer options, C is the correct examination response.

Application Roles manage authorization membership rather than active sessions. Save Content with HTML Markup is a specific security privilege controlling whether HTML-bearing content can be saved. Manage Privileges configures functional privileges but doesn't itself provide the active-user session list. Catalog monitoring similarly doesn't answer the requirement to enumerate currently signed-in users.

Therefore, Manage Sessions is the correct functional capability, with Sessions and Query Logs being the current OAC Console presentation of that functionality.

Reference Topic: Managing Administration, Security, and Performance — Monitoring Users and Sessions

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

Oracle provides a specific Dashboard Builder procedure for displaying a list of briefing books . The briefing books should be stored in a catalog folder. The dashboard author then drags a Folder object from the Dashboard Objects pane into the required dashboard section and opens its properties. In Folder Properties , the author specifies the folder containing the briefing books.

At runtime, the Folder object presents the folder's available briefing books to authorized users. Oracle also allows the author to control whether the folder initially appears expanded.

The Add to Briefing Book option performs the opposite task: it adds dashboard-page or analysis content into a briefing book rather than displaying a collection of existing briefing books. Downloading individual PDF versions likewise doesn't create a dashboard-accessible list. Saved Customizations preserve dashboard state and prompt selections, not catalog-folder contents.

Oracle's documented workflow directly specifies: add a Folder object, open Folder Properties, and identify the folder containing the briefing books. Therefore, option A precisely implements the required dashboard behavior.

Reference Topic: Designing, Creating, and Enhancing Dashboards — Briefing Books and Folder Objects

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

The appropriate Publisher destination is FTP Delivery . Oracle Analytics Publisher supports FTP as one of its standard scheduled report-output destination types. After an administrator configures the FTP delivery infrastructure, report-job authors can select FTP in the Schedule Report Job page and provide the required destination information.

The FTP destination is intended specifically for transferring generated report output to a remote file server. Oracle's scheduling documentation lists FTP alongside destinations such as Email, Printer, Fax, Content Server, and other configured delivery mechanisms. Authentication information such as a valid user name and password is required when defining the FTP destination.

This means a successfully generated PDF, spreadsheet, text file, or other supported output can be automatically transferred to the designated FTP location as part of the scheduled job workflow.

A Dashboard Prompt only collects runtime filtering selections. Narrative View is an analysis-result presentation format, while an Action Link initiates navigation or other actions from analytical content. None provides scheduled file-transfer delivery.

Therefore, the correct delivery mechanism for this requirement is A. FTP Delivery .

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

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

Catalog translation in Oracle Analytics Publisher follows an export–translate–import process based on XLIFF. The administrator first exports the translatable strings for a selected catalog folder. After the XLIFF content is translated, the translated file must be imported back for that catalog folder using the Translation functionality.

Displaying those translated catalog strings also depends on the user's language preference. Oracle distinguishes catalog interface translations from report-output locale. Catalog object names, descriptions, parameter names, and similar catalog strings are presented according to the user's selected UI Language . Therefore, users must choose the corresponding target language in their account preferences to see the imported catalog translation.

Uploading the file as an RTF template would invoke a different template-localization process. Rebuilding the layout is unnecessary because XLIFF localization separates translated strings from the base object. A BI Presentation Server restart is not part of Oracle's prescribed translation workflow. Changing the source language attribute is likewise not the required mechanism.

Accordingly, importing the translated XLIFF and selecting the corresponding UI Language are the necessary steps.

Reference Topic: Managing Report Scheduling, Data Sources, Administration, and Translations — Catalog Translation and XLIFF

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