1z0-1177-26 Governed Analytics Professional with Oracle Analytics Cloud Questions and Answers

XLIFF translation files are Oracle Analytics Publisher's standard mechanism for translating textual content in report templates. XLIFF—XML Localization Interchange File Format—contains translatable strings such as report titles, table headers, labels, and other boilerplate text that appears in generated output.

Publisher can extract those strings from an RTF template, allow them to be translated into one or more languages, and then associate each translated XLIFF file with the original template under the corresponding locale. At runtime, Publisher evaluates the user's selected Report Locale and automatically selects the matching localized template or XLIFF translation according to its locale fallback rules.

This supports a single underlying report definition while presenting labels in French, Japanese, English, or other configured languages.

Report Bursting controls splitting and delivery rather than language translation. Repository Variables store shared semantic values, while Dashboard Prompts collect user selections and don't provide template-localization infrastructure.

Therefore, XLIFF translation files directly satisfy the requirement for automatically localized report labels based on the user's selected language or report locale.

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

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

Sensitive salary information must be protected through data-level authorization , not merely hidden through visual formatting. The supplied source therefore correctly identifies security applied to the report's data access together with appropriate user or role permissions as the strongest approach.

Oracle Publisher security separates access to functionality, catalog objects, and data sources. Roles can be granted or denied access to particular data sources, while catalog permissions determine who may read or execute report objects. For more granular row-level protection, Publisher can also work with database-enforced mechanisms such as Virtual Private Database policies, as covered elsewhere in the source.

Conditional Formatting is only a presentation mechanism. Hiding a salary column visually doesn't constitute access control if the unauthorized data is still retrieved or otherwise available in report output. Personal Folders restrict catalog sharing but aren't a scalable data-security architecture, and disabling scheduling doesn't affect online access to salary information.

Accordingly, security should be applied at the data-access/data-model layer and reinforced with role-based permissions , making A the correct answer.

Reference Topic: Managing and Securing Oracle Analytics Publisher — Data Access Security and Report Authorization

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

Oracle Analytics provides explicit content-ownership and catalog-property administration. Authorized users and administrators can change or reassign ownership of catalog content. Oracle's Content Management functionality supports assigning content to another user or, for certain object categories, an application role. Classic Catalog also provides ownership operations for supported reporting content.

Catalog items can additionally be designated Read-Only through their properties. Oracle gives the example of making an analysis read-only so other users can't modify it. Thus, D is directly supported.

By contrast, My Folders is private storage . Current Oracle Analytics documentation states that other analytics users can't access content stored there. Content that must be shared should be saved or moved to Shared Folders and given appropriate access permissions. Different object types aren't required to reside in separate folders, and catalog content can be copied, moved, archived, or unarchived subject to privileges and object capabilities.

Therefore, the Oracle-documented answers are A and D . The uploaded file marks A and C, but C conflicts with current Oracle Analytics documentation on My Folders privacy and is therefore corrected here.

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

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

Before migrating a semantic model to Oracle Analytics Cloud, database connection information in every relevant connection pool must be updated for the cloud database. Oracle specifically requires the Call Interface to be Oracle Call Interface (OCI) for Oracle Database connections. In addition, for Oracle Analytics Cloud migration scenarios, the Data Source Name must contain the full connect string for the database containing the replicated data.

Oracle's current semantic-model migration guidance is explicit that a net service name isn't sufficient in this OAC scenario. This differs from some Oracle Analytics Server deployments where tnsnames.ora aliases can be supported. The cloud migration workflow therefore requires administrators to examine each connection pool, not merely the first connection associated with a database object.

ODBC isn't the recommended Oracle Database interface for this configuration, and restarting the BI Server after every individual connection-pool modification isn't part of the specified preparation procedure.

Thus, the required combination is OCI as the call interface and the complete database connect string as the Data Source Name , exactly matching D and E.

Reference Topic: Connecting to Data Sources and Migrating Artifacts — Preparing Semantic Models/RPDs for Oracle Analytics Cloud

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

Action Links enable context-sensitive navigation from analytical content to related analyses, dashboards, web pages, or other supported targets. An action link can be associated with a column heading, column value, or hierarchy-level value in an analysis. When invoked, the link can pass mapped parameters or contextual information to the destination.

This makes Action Links appropriate for moving from a summarized analytical view into transaction-level detail. For example, a user could select a customer, product, opportunity, or regional value in a summary analysis and open a detailed destination that reflects the selected context. Oracle's Action Framework supports parameter mapping when configuring the target action.

Modern Oracle Analytics workbook Data Actions provide a comparable capability: Analytics Links can pass source-canvas context into another canvas or workbook. The classic Action Link remains the feature explicitly represented in this question.

Repository Variables contain centrally managed values but aren't navigation mechanisms. Runtime Configuration controls Publisher processing settings, and Bursting generates and distributes personalized Publisher documents.

Therefore, B. Action Links is the correct mechanism for contextual navigation from summary to detailed analytical information.

Reference Topic: Designing, Creating, and Enhancing Dashboards — Action Links and Contextual Navigation

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

The most effective combination is query caching plus an optimized semantic model . Oracle Analytics query caching stores previously generated query results so that compatible subsequent requests can be satisfied without repeatedly executing equivalent SQL against the underlying database. This reduces database workload, network traffic, and analytical response time for frequently repeated requests.

Caching alone, however, is not a substitute for sound semantic-model design. Proper logical relationships, aggregation behavior, source mappings, calculations, and physical connection configurations influence the efficiency of generated queries. Optimizing the model therefore addresses the cost of queries that do reach the source, while caching prevents unnecessary repetition of previously resolved requests.

Oracle also emphasizes that administrators need an appropriate cache-management strategy. Cache entries must be invalidated when source data or semantic-model definitions change so that users don't receive stale results.

Disabling caching increases database load. Duplicate subject areas add administrative complexity without inherently improving performance. Running every analysis every minute can substantially increase processing rather than reduce it.

Therefore, C provides the correct performance architecture: optimize query generation and use caching to avoid unnecessary source executions.

Reference Topic: Managing Administration, Security, and Performance — Query Cache and Semantic Model Performance

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

The Oracle Analytics Catalog serves as the organized repository for analytical content. It stores and manages objects that users create and consume, including analyses, dashboards, prompts, Publisher reports, data models, templates, and related analytics artifacts. Content is organized into folder structures and governed through object-level access permissions.

Oracle distinguishes between personal and shared catalog locations. My Folders contains content belonging to an individual user, while Shared Folders contains objects intended to be accessible to authorized users or groups. The Catalog also supports operations such as searching for content, assigning permissions, moving or copying objects, and—in Publisher scenarios—uploading, downloading, and managing translations.

The Catalog isn't a relational database repository and therefore doesn't store database indexes or physical database schemas as its core purpose. It also doesn't generate warehouse tables or replace Oracle Database security. Database-level access control remains separate from analytics-content authorization.

Consequently, option B accurately describes the Catalog as the central organizational and management facility for Oracle Analytics content.

Reference Topic: Understanding Oracle Analytics Cloud — Catalog and Analytics Content Management

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

A Top N selection/filtering operation is the feature designed to retain only the highest-performing members according to a selected measure. In this case, Product Category is the dimension and current-quarter Sales is the measure used to rank the categories. Configuring the analytical selection to retain the top five categories produces exactly the required comparison population.

Oracle Analytics supports both selection-step member refinement and explicit Top/Bottom N filtering capabilities. The current Oracle Analytics documentation includes Top N examples that identify the highest attribute values based on a measure, which is precisely the analytical pattern in this question.

The important concept is that the ranking is based on the measure rather than visual styling. Conditional Formatting could visually distinguish high or low Sales values but wouldn't restrict the result to five product categories. Repository Initialization Blocks initialize semantic-model variables and have no role in ranking members. Dashboard Page Style controls appearance and layout rather than result membership.

Therefore, Selection Step with Top N filtering is the best supplied answer because it limits the displayed product categories according to their current-quarter Sales ranking and retains only the five highest performers.

Reference Topic: Formatting Data and Managing Filters, Selection Steps, and Variables — Top N Analysis

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

A List of Values (LOV) parameter provides the controlled runtime selection required in this scenario. In Oracle Analytics Publisher, a developer first defines a List of Values, which can contain either fixed values or values returned dynamically by a SQL query. The developer then creates a Menu parameter and associates that parameter with the LOV.

For a Department prompt, the LOV might return Department Name as the user-facing label and Department ID as the value passed into the report query. The selected value can then be referenced through a bind variable, allowing the underlying data set to retrieve only data corresponding to the user's department selection.

Oracle Publisher parameters support interaction with report data at runtime, while Menu parameters specifically present predefined lists. This provides controlled input and prevents users from entering arbitrary department identifiers.

Bursting is concerned with splitting and distributing report output. Translation functionality localizes report content. Layout Editor controls report presentation rather than query parameters.

Therefore, the feature that satisfies a predefined department selection before query execution is the List of Values parameter mechanism , making D correct.

Reference Topic: Exploring and Creating Reports and Data Models — Parameters and Lists of Values

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

The correct mechanism is to assign catalog permissions based on application roles . Oracle Analytics Publisher authorization combines functional roles with catalog permissions. A user may possess general Publisher functionality, but access to a particular catalog object still depends on permissions granted for that report and its containing folders.

For this scenario, an HR Manager application role can be granted the required Read and Run Report Online permissions for the payroll-report folder or individual reports. Other authenticated users should not receive those permissions. Oracle recommends role-based administration because managing group or role membership is substantially more scalable and auditable than maintaining permissions individually for every user.

Oracle also emphasizes that roles with functional privileges can't perform catalog actions unless they possess the corresponding catalog permissions. This makes catalog security the correct control point for protecting sensitive payroll reports.

Query caching affects performance rather than authorization. Dashboard Prompts filter runtime values but aren't security boundaries. Separate report layouts change presentation and don't prevent unauthorized execution.

Therefore, C. Assign catalog permissions based on application roles provides the required role-based report access control.

Reference Topic: Managing and Securing Oracle Analytics Publisher — Roles and Catalog Permissions

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

Successful authentication proves the user's identity, but it does not automatically authorize access to Publisher catalog content. Oracle explicitly distinguishes authentication from authorization: after a user is authenticated, access to Publisher resources is controlled through application-role mappings, permission grants, catalog permissions, and associated security policies.

Following migration, the administrator should therefore verify that users or groups are correctly mapped to the expected application roles and that those roles retain the necessary catalog permissions on the shared Publisher folders, reports, data models, and any dependent catalog objects. Oracle notes that a role with functional Publisher privileges still can't act on catalog objects until the corresponding catalog permissions are granted.

Database optimizer statistics might affect query performance but wouldn't normally produce a Publisher authorization error. Dashboard layout controls presentation, and browser caching doesn't determine application-role authorization.

The uploaded source's own explanation confirms this authentication-versus-authorization distinction, although its extracted Correct Answer marker is displaced. Oracle documentation independently confirms that Catalog permissions and application role assignments are the first security area to inspect.

Reference Topic: Managing and Securing Oracle Analytics Publisher — Authentication, Authorization, Roles, and Catalog Permissions

An Action Link Menu is designed specifically for grouping several dashboard actions behind one visible menu. Instead of displaying multiple independent links, the author places an Action Link Menu object on the dashboard and adds the individual action links to that menu. Each contained action can navigate to another analytics object, external web page, or other supported destination.

The Menu Label supplies the text displayed to the user for that grouped menu. Oracle's configuration workflow explicitly instructs authors to enter a value in the Menu Label field and then add individual action links to the Action Link Menu. When the consumer uses the menu, the available actions are presented as selectable options.

Standalone inline or named links would expose multiple separate links and therefore violate the requirement for one visible entry point. The More icon is not the dashboard design mechanism required here, and creating separate dashboard pages introduces unnecessary navigation and maintenance.

Therefore, the correct design is to use an Action Link Menu as the container and configure its Menu Label as the visible menu text.

Reference Topic: Designing, Creating, and Enhancing Dashboards — Action Links and Action Link Menus

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

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

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

Oracle Analytics Cloud uses snapshots , which can be exported as BAR files , to provide a controlled and repeatable mechanism for migrating analytics content between environments. A snapshot can package supported service content and configuration, including catalog objects such as dashboards and analyses, Publisher artifacts, semantic-model content, application-role information, and other applicable configuration.

Oracle's documented migration workflow is to create a snapshot in the source environment, export the snapshot as a .bar file, import that BAR file into the target Oracle Analytics Cloud instance, and then restore the required components. The Custom restore option allows administrators to select which elements are transferred when the target environment contains configuration that must remain unchanged.

Manual catalog copying does not provide the same dependable migration of dependencies and service configuration. Recreating dashboards in production is inefficient and prone to configuration drift. PDF files are generated outputs and cannot recreate Analytics or Publisher objects.

Therefore, the repeatable Oracle-supported deployment mechanism represented in the choices is exporting and importing a snapshot using a BAR file .

Reference Topic: Connecting to Data Sources and Migrating Artifacts — Snapshots and BAR Migration

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

The technically correct combination is A and E . Oracle Analytics Publisher implements cascading parameters primarily through a Menu parameter backed by a List of Values , together with the Refresh other parameters on change option. Oracle states that Menu parameters support partial-page refresh for cascading parameters. When Refresh other parameters on change is enabled on the controlling parameter, Publisher performs a partial refresh of other parameters whose available values depend on the changed value.

For example, a Department Menu parameter can control an Employee Menu parameter. When Department changes, Publisher reevaluates the dependent employee LOV and presents only employees belonging to the selected department.

Multiple Selection does not create or enable cascading behavior. It merely allows more than one value to be chosen from a parameter's list. Therefore, option D in the uploaded source key should not be treated as the mechanism that establishes the dependency. A Date parameter does not provide the required LOV-based cascading model, while Fixed Data does not dynamically reevaluate dependent values.

Accordingly, this question requires a correction from the supplied key: Refresh other parameters on change + Menu parameter is the Oracle-documented implementation.

Reference Topic: Exploring and Creating Reports and Data Models — Cascading Parameters and Lists of Values

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

Template Builder for Microsoft Word provides dedicated translation tools for extracting translatable text from an RTF template into an XLIFF (.xlf) file . Oracle's documented procedure is to open the template with Template Builder installed and, from the Template Builder tools, choose Translation → Extract Text . Publisher then extracts the template's translatable boilerplate strings and creates an XLIFF file.

Typical translatable strings include report titles, table headers, field labels, and static textual content intended to appear in generated output. Data supplied dynamically at runtime isn't extracted as template translation text.

The resulting XLIFF file can then be provided to a translator or edited with an XLIFF-compatible tool. After translation, it is associated with the original report template for the appropriate locale. Preview Translation is used later to test an already-created translation; it doesn't generate the initial XLIFF file. Uploading a localized RTF file represents a different localization strategy. Changing the user's report locale also doesn't perform text extraction.

Thus, Translation → Extract Text is the specific Template Builder command that creates the XLIFF translation file.

Reference Topic: Building and Formatting Reports Using Layout Editor and Template Builder — XLIFF Translation

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

Query Builder provides a graphical mechanism for defining relational SQL data sets. When multiple tables are involved, the developer must first establish the logical relationship between them. Typically, this means creating a join using matching columns , such as a parent table's primary key and a child table's corresponding foreign key.

After the tables and relationships are established, the required output fields are selected by choosing the check boxes beside the column names in Query Builder's design interface. Those selected fields become part of the generated SELECT list. Oracle's Query Builder documentation and examples show precisely this pattern: create the relationship between tables, select the desired columns, optionally define conditions and sorting, and then save the generated SQL.

A report definition doesn't need to be created before building the query. Dashboard definitions are unrelated to Publisher SQL Query datasets. Sample-data generation occurs after the query has been defined sufficiently to execute, and parameters are optional rather than prerequisites for creating table relationships.

Accordingly, the two essential query-definition operations are joining the related tables and selecting the required columns , making C and E correct.

Reference Topic: Exploring and Creating Reports and Data Models — Query Builder, Joins, and Column Selection

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

The required configuration combines Show Apply Button = False with a Checkboxes parameter presentation. Oracle Analytics Publisher defines the Show Apply Button property as controlling whether users must explicitly submit changed parameter values. When this property is set to False, Publisher removes the Apply button and automatically regenerates the report after a parameter selection or entry changes. This directly satisfies the requirement for immediate rendering.

Checkboxes are appropriate for the second requirement because they permit the user to select multiple parameter values. Oracle’s Report Viewer documentation identifies check boxes as a prompt control specifically intended for multiple selections. By contrast, Parameter Location and Parameter Label Location affect only the visual positioning of parameter controls and labels; they have no effect on refresh behavior or selection cardinality. Disabling a general Show property would suppress controls rather than implement automatic parameter processing.

Therefore, D controls when the parameter change is applied , while E controls how many values the user can select . Together they satisfy both functional requirements.

Reference Topic: Oracle Analytics Publisher — Report Parameters and Report Viewer Configuration

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

Adding a Calculated Column allows an analysis author to derive a new analytical value from existing columns or expressions without changing the underlying physical source data. The calculation becomes part of the current analytical definition and can be referenced throughout the analysis where supported.

Calculated expressions are useful for metrics such as profit percentage, variance, adjusted revenue, unit price, ratios, and other values derived from existing measures or attributes. This provides flexibility at the content-authoring layer while leaving centrally governed semantic-model objects unchanged.

The scope described in the question is important: the calculation must remain reusable within the current analysis . If the organization needed the metric governed and reusable across many analyses, defining the calculation centrally in the semantic model would normally provide stronger enterprise consistency.

A Dashboard Prompt supplies runtime values and filtering rather than creating calculated metrics. BAR files are migration artifacts and don't constitute an analysis calculation mechanism. Application Roles control authorization and permissions.

Therefore, among the available choices, Adding a Calculated Column is the function that creates the required derived metric in the analysis. The uploaded question explicitly associates this behavior with a calculated column.

Reference Topic: Managing and Creating Analyses, Views, and Content — Calculated Columns and Derived Metrics

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

Oracle Analytics Publisher layouts can contain multiple report components within the same layout , allowing different representations of a report's data to be assembled into a single formatted document. The Layout Editor Components pane includes visual and tabular components such as charts, pivot tables, tables, images, and other elements that can be dragged into the report layout.

For this finance-report requirement, the author can place a summary chart near the top, use a pivot table for multidimensional financial analysis, and include a conventional table for transaction-level detail. Layout grids and other layout controls can be used to position these components appropriately within the report.

A Dashboard Prompt is intended for runtime filtering and doesn't construct Publisher layout sections. Repository Variables provide centrally managed values rather than report-design components. Data Gateway supplies remote source connectivity.

Oracle documentation explicitly states that Layout Editor provides a drag-and-drop interface and that its Components pane includes objects such as charts and pivot tables. This architecture supports combining the required presentation elements within one report.

Therefore, C. Multiple layout components within a single report is correct.

Reference Topic: Building and Formatting Reports Using Layout Editor and Template Builder — Layout Components

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

Creating the PL/SQL policy function alone doesn't activate Virtual Private Database protection. The function must be associated with the database object that requires protection. Oracle uses the DBMS_RLS.ADD_POLICY procedure to attach the VPD policy and its policy function to a table, view, or synonym. Once associated, Oracle Database automatically incorporates the policy predicate whenever relevant SQL accesses that object.

The implementation should then be tested directly at the database layer , using a SQL client such as Oracle SQL Developer. Testing with different application or proxy-user contexts confirms that the predicate returns the intended row subsets before Publisher reporting depends on the security configuration.

Catalog roles don't substitute for VPD because catalog permissions protect report objects rather than rows inside database tables. Creating separate reports for individual users would duplicate content and fail to implement centralized row security. Proxy authentication is often useful with Publisher because it preserves individual identity for database-side security enforcement, so disabling it isn't the appropriate completion step. A database restart isn't normally required after attaching a VPD policy.

Thus, the correct database-side actions are apply the policy to the target table and validate its behavior using a SQL tool .

Reference Topic: Managing and Securing Oracle Analytics Publisher — Implementing and Validating VPD Policies

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

The two fundamental bursting keys are Split By and Deliver By/Delivery By . The Split By element identifies how the report data is divided into individual blocks. For example, when producing customer invoices, CUSTOMER_ID can be used as the Split By value so that a separate data block and document can be generated for each customer.

The Deliver By element determines how formatting and delivery information is associated with each split segment. Oracle's bursting engine uses this key to correlate each section with information returned by the delivery query, including template, output format, locale, delivery channel, destination, and other delivery parameters. Consequently, different recipients can receive differently formatted outputs through different delivery channels from a single report execution.

Bursting definitions belong to the Publisher data model , not exclusively to the scheduling interface. Bursting is also not restricted to one output format across all generated documents. Supported delivery mechanisms extend beyond FTP and can include email, printers, content repositories, and other configured destinations. The Diagnostic tab is not where the bursting delivery query is conceptually defined.

Thus, Split By controls data segmentation , while Delivery By controls segment-specific formatting and distribution .

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

A Publisher subtemplate is specifically intended to centralize reusable layout and processing components so that they can be referenced from multiple report templates. Oracle defines a subtemplate as formatting functionality that is created once and reused either multiple times in one layout or across multiple report-layout files.

Common Oracle-documented use cases include reusable headers, footers, address blocks, conditional layouts, calculations, and formatting logic . Corporate branding and standard legal disclaimers fit this design precisely. The developer can create an RTF subtemplate containing the standardized components, upload it as a Sub Template object in the Publisher Catalog, and then import and call the required template sections from individual RTF layouts.

If company branding or legal language changes, updating the centralized subtemplate minimizes maintenance across all reports that reference it.

Duplicating the content in every RTF layout creates consistency and maintenance problems. Separate layouts still duplicate common material. SQL data models should represent data retrieval and structure, not presentation branding.

Therefore, C. Create a subtemplate and reference it from report templates is Oracle's recommended reusable-design pattern.

Reference Topic: Building and Formatting Reports Using Layout Editor and Template Builder — RTF Subtemplates

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

Pixel-Perfect Reporting with Bursting is specifically designed for high-volume personalized document generation and distribution. Oracle Analytics Publisher executes the underlying report query, splits the resulting data according to a configured Split By key, generates a separate document for each resulting block, and determines formatting and delivery through the bursting delivery definition.

This architecture is well suited to producing 3,200 individualized sales reports. A sales-representative identifier can act as the bursting key, allowing one report definition and one data-extraction process to generate separate reports for each representative. Each segment can also use destination-specific delivery information, templates, output formats, locale settings, and delivery channels.

Oracle documents analogous bursting use cases such as generating individual cost-center reports for managers, customer invoices with customer-specific delivery preferences, and payslips for all employees from one extract. The same design pattern applies directly to thousands of sales representatives.

SMTP only provides an email transport mechanism; it doesn't perform report segmentation. Smart View is an Office-based analytics client. Agents automate analytical delivery but aren't the Publisher document-splitting technology required here.

Therefore, Pixel-Perfect Reporting with Bursting is the scalable solution.

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

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

Data Gateway is Oracle Analytics Cloud's supported remote-data-connectivity mechanism for accessing eligible on-premises data sources when the data remains within the organization's network. Oracle instructs administrators to install Data Gateway on a host within the network where the data source resides and register it with the target Oracle Analytics Cloud environment.

OAC can then route supported analytical requests through the configured remote connectivity mechanism rather than requiring the database itself to be directly exposed through a public internet endpoint. When creating the OAC database connection, the administrator enables Use Remote Data Connectivity so queries can use Data Gateway.

Oracle's current security guidance identifies both Data Gateway and Private Access Channel as secure approaches for connecting OAC to on-premises data sources. Since Private Access Channel isn't one of the answer choices, Data Gateway is unequivocally the correct response here.

OCI Object Storage is an object-storage platform and doesn't provide the required database-query bridge. FTP transfers files rather than establishing analytical SQL connectivity. A Public REST Endpoint would contradict the requirement to avoid direct internet exposure.

Therefore, the appropriate feature is Oracle Analytics Data Gateway .

Reference Topic: Connecting to Data Sources and Migrating Artifacts — Data Gateway and Remote Data Connectivity

Publisher database connectivity is administered through the Publisher Administration page , not through individual reports or dashboards. In an integrated Oracle Analytics environment, Oracle documents the navigation path through Administration → Manage Publisher to reach the Publisher administration interface.

From there, the administrator uses the JDBC Connection option under Data Sources and selects Add Data Source . The JDBC definition contains configuration such as the data source name, database driver, connection string, authentication credentials, optional proxy authentication, and allowed roles. Once configured successfully, that connection becomes available to authorized Data Model developers when they create SQL Query data sets.

A report layout is downstream of data acquisition and therefore isn't required to establish connectivity. Sample data likewise depends on an executable data model. Dashboard Editor manages dashboard presentation rather than Publisher database connections, while the Catalog stores Publisher objects but isn't the administrative interface for defining JDBC infrastructure.

Consequently, the correct workflow is to access Manage Publisher/Publisher Administration and then create the connection through JDBC Connection under Data Sources .

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

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

A Presentation Variable is the variable type specifically designed to capture a value selected by a user through a dashboard prompt and make that value available dynamically to analyses and other dashboard content.

Oracle states that a presentation variable can be created as part of either a column prompt or a variable prompt . Whenever the user selects one or more values in the associated prompt, Oracle sets the presentation variable to the selected value or values. Analyses can then reference that variable in filters, column formulas, titles, narrative text, or other supported expressions.

In this scenario, selecting Fiscal Year at runtime establishes a user-controlled value that multiple analyses can consume. Because the value changes interactively as the user changes the prompt selection, Presentation Variable is the appropriate variable scope.

A Repository Variable is centrally managed and isn't normally populated from a user's dashboard selection. Session variables generally hold user-specific or system values initialized for a login session. Initialization blocks are mechanisms used to populate certain server/session variables rather than the runtime dashboard variable required here.

Therefore, Presentation Variable precisely matches the described prompt-driven dashboard behavior.

Reference Topic: Formatting Data and Managing Filters, Selection Steps, and Variables — Presentation Variables