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

OCI Object Storage can be configured as an Oracle Analytics Publisher delivery destination, but the Publisher service requires both appropriate OCI permissions and authentication information.

First, the administrator must have access to an OCI compartment in which an Object Storage bucket can be created or used. Oracle documents specific tenancy and compartment permissions for this purpose, including access to the Object Storage namespace and required bucket/object operations.

Second, Oracle's documented configuration workflow instructs the administrator to use the OCI Console to create a bucket and configure an API key for authentication . The associated user, tenancy OCIDs, public-key fingerprint, private key, compartment, and bucket information are then used when defining the Object Storage delivery server in Publisher.

CUPS and fax4CUPS relate to printer/fax delivery rather than OCI Object Storage. An Intradoc URI and Content Server metadata concern Oracle WebCenter Content integration. SMTP is required for email delivery but not Object Storage.

Therefore, compartment/bucket access and an OCI bucket authenticated through an API signing-key configuration are the two prerequisites directly associated with this Publisher delivery channel.

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

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

The scheduled job instance is skipped . Oracle Analytics Publisher defines a Schedule Trigger as a SQL query that is executed when the scheduled report job is triggered, before the report itself runs. The returned result determines whether the execution condition has been satisfied.

Oracle states explicitly that if the trigger SQL returns data , the associated report job executes. If the SQL query returns no data , the job instance is skipped. This mechanism allows report execution to depend on a business or technical condition. For example, a report could execute only after an ETL process has completed, only when transactions exceed a specified amount, or only when new records have appeared.

The trigger doesn't convert the job into a bursting job, nor does Publisher execute an empty report merely with a warning. The scheduled job definition also isn't deleted; only that execution instance is skipped. For recurring schedules, subsequent trigger evaluations can still occur according to the configured recurrence and retry behavior.

Therefore, a no-row result from the Schedule Trigger means its condition evaluated as not satisfied and the current job instance is skipped .

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

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

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

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

Drilling on an attribute column performs what Oracle describes as a filter drill . When the user clicks a drillable attribute value, Oracle adds the next lower level to the displayed analysis and creates a filter corresponding to the member on which the user drilled.

Oracle's documentation states that drilling in an attribute column affects all relevant views. After the value is clicked, a column is added to the analysis and a filter is automatically created and listed on the Criteria tab . This distinguishes attribute-column drilling from drilling in hierarchical columns, where expanding or collapsing hierarchy members generally affects only the particular hierarchy view without creating the same analysis-wide filter drill behavior.

The drill operation therefore modifies the analytical context; the underlying criteria don't simply remain unchanged. Oracle also doesn't automatically save the resulting drill filter as a reusable named filter, nor does a drill operation create a dashboard prompt. Those are separate authoring operations.

Consequently, the specific outcome described by Oracle is exactly option A: drilling an attribute column automatically introduces the corresponding filter and adds the lower-level column to the analysis criteria.

Reference Topic: Managing and Creating Analyses, Views, and Content — Drilling in Analysis Results

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

Oracle Analytics supports cross-subject-area analyses , so the appropriate approach is to create the analysis using the primary subject area and then add another compatible or related subject area through the Analysis Editor.

Oracle's documented workflow starts by selecting one subject area and adding the initial analysis columns. The author then uses Add/Remove Subject Areas in the Subject Areas pane to include another subject area and select the additional required columns. Where local dimensions are involved, Oracle recommends including an appropriate measure from each participating subject area so that the semantic model can resolve the query correctly.

The Analysis Editor is therefore capable of querying multiple subject areas when the semantic relationships support the requested combination. Modifying the semantic model simply to expose every required column in one subject area is unnecessary when compatible subject areas already exist. UNION is a set operation used for combining compatible result sets and is not the standard mechanism for selecting related columns across subject areas. MERGE and dashboard prompts likewise do not establish semantic relationships.

Thus, the supported workflow is to create one analysis and add the second related subject area.

Reference Topic: Managing and Creating Analyses, Views, and Content — Cross-Subject-Area Analyses

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

Customized regional marketing reports represent an appropriate bursting use case because bursting is intended to take a single report data set, divide it into logically distinct sections, generate separate documents, and deliver those documents according to segment-specific criteria.

For example, an organization could retrieve enterprise marketing performance in one query and split the resulting data by Region. Publisher could then generate one report for Europe, another for North America, another for Asia-Pacific, and so forth. Each segment could be delivered to the appropriate regional manager and could use its own locale, output format, template, or delivery destination.

Oracle's documented bursting examples follow precisely this pattern: customer-specific invoices, separate financial reports for cost-center managers, and individualized employee payslips. Customized regional reports are another application of the same key-based segmentation and delivery architecture.

Bar codes and government PDF forms are valid pixel-perfect reporting scenarios but don't inherently require bursting. Interactive data exploration is associated with analytical visualization, and ad hoc reporting refers to dynamically created analyses rather than mass personalized document generation.

Therefore, customized regional marketing reports are the choice that directly demonstrates Publisher bursting.

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

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

Agents are the intended Oracle Analytics capability for automatically executing analytical content according to a schedule or business condition and then delivering the resulting information to users or configured destinations. An agent can run periodically, evaluate a condition, select analytical content, identify recipients, and determine delivery destinations.

For example, an agent can evaluate an analysis each morning and deliver an alert only when inventory drops below a defined threshold. Oracle's current Oracle Analytics Cloud interface increasingly uses the term Delivery for this functionality, but the underlying scheduled/conditional delivery framework is the same capability historically identified as Agents in Classic Analytics.

Selection Steps control which members appear in analysis results. Trellis Views provide repeated comparative visualizations. Subject Areas expose governed business data from the semantic model. None of those features performs condition-driven scheduled delivery.

There is an internal error in the uploaded source: the placement of its “Correct answer” marker makes Selection Steps appear keyed, while the source explanation explicitly says that Agents automate execution and distribution based on schedules or conditions . Oracle documentation supports Agents/Deliveries, so the verified answer is A .

Reference Topic: Managing Administration, Security, and Performance — Agents, Deliveries, Conditions, and Scheduling

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

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 principal risk is that COUNT DISTINCT, AVG, and similar calculations can produce unexpected or different results when Publisher receives data that has already been summarized by Oracle Analytics . When a report is created directly against a subject area, the BI Server performs semantic-model processing and aggregation before delivering the result set to Publisher. Publisher therefore does not necessarily receive the original detailed rows required to reproduce certain aggregate calculations accurately.

Oracle specifically cautions that subtotals and totals for subject-area reports are based on data already summarized by the BI Server. Functions requiring access to the original column-level data—Oracle explicitly identifies count distinct and average —can consequently return different results when reapplied within Publisher.

A data model is not mandatory when directly creating a subject-area report; direct subject-area reporting is specifically supported. Hierarchical columns are also not required and, in fact, have limitations in Publisher subject-area reports. The Create Report guide can directly query a subject area without requiring an intermediary Publisher data model.

Therefore, designers must understand the grain and aggregation state of data received from the semantic layer before introducing additional aggregate calculations.

Reference Topic: Exploring and Creating Reports and Data Models in Oracle Analytics Publisher — Subject Area Reports

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

Oracle Virtual Private Database (VPD) implements fine-grained, database-level access control by dynamically restricting rows returned to a user. A VPD policy associates a policy function with a protected table, view, or synonym. When a SQL statement references that object, Oracle Database automatically applies the policy-generated predicate to the statement.

For example, a query that conceptually requests every row from a sales table can transparently become a query restricted to the current user's authorized sales region. This makes VPD particularly suitable for reporting environments where multiple users execute similar reports but must see different subsets of the underlying data.

Oracle Analytics Publisher can preserve user identity through proxy-authenticated connections, while the database's VPD policy performs the row-level enforcement. This is fundamentally stronger than filtering sensitive rows only after they have already been returned to Publisher.

Catalog permissions solve a different security problem: they determine who can access or modify report objects. Bursting creates personalized documents but doesn't constitute database row-level security.

Therefore, VPD's defining role in this scenario is database-enforced row-level security , making A correct.

Reference Topic: Managing and Securing Oracle Analytics Publisher — VPD and Row-Level Data Security

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

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

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

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

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

The most maintainable approach is to retain a single dashboard design while using dashboard filtering together with security controls that ensure each manager sees only authorized data. Dashboard prompts can provide a common interactive filtering experience, while row-level or role-based security must enforce the actual access boundary.

Oracle Analytics supports application-role-based filtering so that different users opening shared analytics content see only the data applicable to their assigned role. Oracle also supports object and data-access permissions through application roles and semantic-model security. This means the organization can maintain one dashboard instead of creating separate copies for every regional manager.

It is important to distinguish functionality from security: a dashboard prompt alone isn't an authorization mechanism . The security filtering component must enforce which regional data each manager is entitled to access. The prompt can then support user interaction within that permitted dataset.

Duplicating dashboards increases maintenance effort and creates version drift. Separate subject areas for each individual manager are also unnecessarily complex, while static PDF exports eliminate interactive analytics.

Therefore, D is the maintainable architecture: one dashboard, shared interaction design, and centrally enforced security filtering .

Reference Topic: Designing, Creating, and Enhancing Dashboards — Shared Dashboard Design and Security Filtering

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

Action Links provide context-sensitive navigation and action execution within Oracle Analytics. They can navigate to BI content, open external web resources, or invoke other supported actions. Presentation variables can participate in navigation scenarios so that contextual values captured at runtime can be supplied when moving between analytical content.

Oracle also explicitly supports conditional Action Links . When an action link is associated with an analysis column, its availability can be controlled by one or more conditions. For example, an escalation action could appear only when Revenue falls below a specified threshold. Oracle documentation describes this as conditionally enabling or displaying the action link according to data-driven criteria.

The remaining statements impose restrictions that do not exist. Action destinations are not limited merely because analyses reside in different catalog folders. Action Links are not restricted to analyses based on one subject area and certainly are not limited to dashboard prompts. Oracle explicitly supports navigation actions that open web pages and other external resources.

Consequently, B and C describe supported Action Link capabilities: runtime contextual navigation and conditional availability.

Reference Topic: Designing, Creating, and Enhancing Dashboards — Action Framework and Conditional Action Links

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

Action Links provide context-sensitive navigation from one Oracle Analytics object to another. When an action is attached to a column value, heading, graph value, or other supported element, the user can invoke the action and navigate to another analysis, dashboard, or external destination. Parameters can be mapped so the target receives contextual information from the source.

In the scenario, the selected Customer ID must follow the user into the detailed customer analysis. Presentation variables are one supported method for maintaining or referencing runtime context in analyses and dashboards, while Action Framework parameter mapping supplies the navigation behavior. Together, these mechanisms allow the target analysis to open already constrained to the relevant customer.

Current Oracle Analytics documentation also describes modern Data Actions as passing context values to target canvases and workbooks, reinforcing the same context-preserving navigation principle.

Repository Variables are centrally managed and not primarily intended for transferring a user's selected customer context. Publisher Bursting creates and distributes personalized documents. Snapshot Migration transfers environment artifacts rather than runtime navigation values.

Therefore, among the available choices, Action Links with Presentation Variables is the correct implementation.

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

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

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

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

Among the provided choices, Selection Step is the intended answer. Selection steps allow an analysis author to refine which attribute or hierarchy members remain visible and can be arranged in a defined sequence. They support operations such as keeping or removing members and applying condition-based member selection, including conditions based on measures such as Sales.

Oracle distinguishes selection steps from conventional filters. A normal column filter is applied before query aggregation , while selection steps operate after aggregation and affect the members displayed without changing already-calculated aggregate values. Selection steps can also be sequenced so that one refinement occurs before a later Top N or other member-selection operation.

There is a wording weakness in this item. If “before any ranking” means before query aggregation and ranking at the SQL level, a conventional analysis filter such as Sales < > 0 would be the cleaner technical mechanism, but Filter isn't one of the answer choices . Of the listed options, Selection Step is the only feature capable of removing members as part of analytical result refinement.

Dashboard Prompts provide runtime input; Conditional Formatting only changes appearance; Narrative View controls presentation.

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

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

Conditional Formatting is specifically designed to modify the visual representation of data when defined conditions are satisfied while leaving the underlying values unchanged. The analyst can establish rules such as Sales greater than or equal to Target and apply one format, while values below Target receive a different format.

Oracle Analytics supports conditional rules based on measures, attributes, thresholds, percentages, and expressions. Formatting can include font characteristics, cell presentation, images, backgrounds, and visualization-specific properties. Oracle's examples include stoplight-style formatting in which low, medium, and high values receive different visual treatments.

This functionality affects presentation only; it doesn't alter the source Sales values or change the actual calculation. That directly satisfies the requirement.

A Repository Variable stores centrally maintained values and isn't itself a visualization rule. Selection Steps determine which members appear after query aggregation. A Subject Area Filter limits the data returned or made available rather than simply changing its appearance.

Consequently, the appropriate feature for showing above-target values in green and below-target values in red is Conditional Formatting , making A correct.

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

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

Oracle Analytics determines the default result view according to the types of columns included in the analysis. Oracle documentation states that when an analysis contains only attribute and measure columns, the Compound Layout initially contains a table . However, when the analysis contains at least one hierarchical column , Oracle automatically creates a pivot table view .

This behavior is intentional because a pivot table is designed to represent hierarchical structures effectively. It supports expansion and collapse of hierarchy members, multidimensional presentation, and hierarchical navigation in ways that a conventional flat table doesn't.

A trellis view is useful for repeated visual comparisons across dimensions but isn't automatically generated merely because a hierarchy is present. Graph and gauge views must generally be added explicitly when appropriate. Likewise, the statement that every analysis defaults to a table is incorrect because Oracle specifically distinguishes hierarchical analyses from analyses containing only attribute and measure columns.

Therefore, once the author selects Results for an analysis containing a hierarchical column, the default result visualization is a Pivot Table . This behavior is directly documented in Oracle's Analysis Results guidance.

Reference Topic: Managing and Creating Analyses, Views, and Content — Hierarchical Columns and Default Views

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

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

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

Analysis criteria are built in the Criteria tab by selecting columns from folders within the chosen subject area. As columns are added, Oracle places them in the Selected Columns pane. The author can then control their sequence directly by dragging selected columns to the desired position.

Column order is significant because it can affect the initial order in which fields appear in certain result views and determines the organizational sequence of criteria. Reordering does not require changing the semantic model or rebuilding the analysis.

Clear Sort removes sorting specifications, such as ascending or descending sort behavior; it doesn't rearrange the position of selected columns. The Results tab is used to inspect and design visual output after criteria have been established. Catalog permissions control object security and aren't involved in analytical column ordering. Column Properties controls formatting, headings, interaction, data format, conditional formatting, and related characteristics but isn't the standard mechanism for rearranging criteria.

Accordingly, the correct workflow is to select the required columns from the subject area and drag them within Selected Columns to establish the desired order . The uploaded Oracle Analytics question source identifies the same workflow.

Reference Topic: Managing and Creating Analyses, Views, and Content — Criteria Tab and Selected Columns

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

The defining characteristic of governed analytics is the use of shared, centrally controlled metadata and business logic. Oracle Analytics semantic models provide a common layer where administrators and data modelers can define dimensions, measures, hierarchies, relationships, calculations, security rules, and business-oriented terminology once and expose those definitions consistently through subject areas.

This avoids a major risk inherent in unmanaged self-service analytics: different users creating different interpretations of the same metric. For example, if each department independently defines Revenue, Margin, Customer Count, or Fiscal Quarter, reports can produce contradictory business results even though they use the same underlying source data.

Governance doesn't mean administrators must create every report. Business users can still independently create analyses, dashboards, and other content against approved subject areas. Nor does governed analytics restrict users to spreadsheets. Instead, governance establishes a controlled semantic foundation while preserving analytical self-service.

Oracle specifically describes the semantic model as a business-oriented abstraction layer that incorporates semantics and governance rules. Therefore, shared metadata and centrally managed business definitions are what most clearly distinguish governed analytics, making D correct.

Reference Topic: Understanding Oracle Analytics Cloud — Governed Analytics and Shared Semantic Metadata

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

Runtime Configuration controls Publisher's system-level processing and document-generation behavior. Oracle's Runtime Configuration framework includes settings for different output types, PDF processing and security, FO processing, memory and performance behavior, template processing, report delivery properties, and associated font mappings.

Oracle's runtime configuration file also illustrates settings such as system-temp-dir, PDF compression, PDF security, and font definitions. In the administrative interface, the Runtime Configuration page provides corresponding system-level properties, with some settings also configurable at individual report level. When report-level and system-level settings differ, Oracle can apply the more specific report-level setting where documented.

A Subject Area is a governed analytical data presentation layer and has nothing to do with Publisher document-processing defaults. Presentation Variables capture runtime prompt values. Selection Steps refine displayed members of an analysis.

The uploaded source's explanation explicitly identifies Runtime Configuration as defining system-wide Publisher processing and output-generation behavior. Its extracted “Correct answer” marker is misplaced relative to the options; Oracle documentation confirms that A. Runtime Configuration is the technically correct answer.

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

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

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

The author should save the filter as a named filter in the catalog . Oracle Analytics distinguishes between inline filters and named filters. An inline filter belongs to one specific analysis, whereas a named filter is stored independently in the Oracle Analytics Catalog and can subsequently be referenced by multiple compatible analyses.

This is particularly useful for centrally reused business criteria. For example, an organization might create a named filter representing a specific State, Quarter, business unit, or product group. Report authors can then apply that saved filter to multiple analyses rather than recreate the filter definition repeatedly. Oracle also notes that when a named filter is edited and saved, changes can propagate wherever the named filter is referenced, improving consistency and maintainability.

Changing AND/OR grouping merely modifies logical relationships between existing filters and doesn't make the filter independently reusable. Drilling changes the current analytical detail level. A dashboard prompt provides runtime filtering but isn't required simply to reuse the same predetermined filter definition.

Therefore, the appropriate reusable object is a Named Filter saved in the Catalog .

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

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

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

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