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

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

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

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

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

A Session Variable is the appropriate choice because its value is associated with an individual user's Oracle Analytics session. Oracle states that session variables are initialized when a user signs in and remain available throughout that user's browsing session. A non-system session variable can therefore hold contextual values such as the user's department, organizational unit, or SalesRegion .

For this scenario, an initialization block can retrieve the user's assigned region during authentication. An analysis can reference that session variable in a data filter, causing each user to receive automatically filtered results without entering a region manually. Oracle explicitly uses user department and sales region as examples of session-variable values.

A Presentation Variable is normally populated interactively through a dashboard or analysis prompt, which violates the requirement for no manual input. A semantic model/repository variable generally holds a value shared more broadly rather than a user-specific login value. A Request Variable temporarily overrides a session variable for an individual request.

Therefore, Session Variable directly provides the required user-specific, login-initialized analytical context.

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

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

Query Builder is specifically designed to construct SQL queries graphically with minimal requirement for manually written SQL. Within the Publisher Data Model Editor, a developer creating a SQL Query data set can launch Query Builder, browse available database objects, add tables or views to the design area, select columns, define relationships between objects, apply query conditions, inspect the generated SQL, and execute the query to review results.

Oracle describes Query Builder as a mechanism for building SQL queries without coding . Its interface separates object selection from query design and output functions, making it suitable for developers or report authors who understand the required data but do not want to manually construct SQL syntax.

Layout Editor serves a different stage of report development: it controls the visual presentation of the report after data has been retrieved. Catalog Manager is concerned with catalog content rather than SQL construction. The Report Wizard assists with creating reports and layouts but is not the graphical relational query-design tool. Parameter configuration defines runtime input values rather than the complete SQL statement.

Consequently, Query Builder precisely satisfies the requirement for graphical SQL development.

Reference Topic: Exploring and Creating Reports and Data Models in Oracle Analytics Publisher — SQL Query Data Sets and Query Builder

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

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

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

A shared Dashboard Prompt with Presentation Variables centralizes user input and allows multiple dashboard analyses to reference the same runtime selection. Oracle defines a Presentation Variable as a variable populated through a dashboard column prompt or variable prompt. Each time the user changes the prompt selection, the presentation variable is assigned the selected value or values.

Analyses on the dashboard can then reference the variable in filters, expressions, titles, or other supported locations. This allows a department, fiscal period, region, or comparable filter criterion to be selected once and reused across multiple dashboard components.

The architecture substantially improves maintainability because the dashboard-level interaction is managed centrally rather than requiring a separate prompt or manually maintained filter mechanism for every analysis. Independent prompts would recreate the exact maintenance problem stated in the scenario. Conditional Formatting changes visual presentation rather than providing shared filtering, while exporting analyses creates static outputs and eliminates the interactive dashboard experience.

Therefore, the correct design is A. Use a shared Dashboard Prompt with Presentation Variables .

Reference Topic: Designing, Creating, and Enhancing Dashboards — Dashboard Prompts and Presentation Variables

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

Selection steps differ fundamentally from conventional filters in their position within analytical processing. Oracle states that filters are evaluated before aggregation , whereas selection steps are applied after the query has been aggregated . As a result, selection steps determine which members are displayed without recalculating the previously established aggregate values.

For example, assume a hierarchy contains members totaling 100. If an ordinary filter removes one member before aggregation, the measure total can change. If a selection step removes that member after aggregation, the displayed membership changes while the aggregate can remain 100. This behavior is precisely why selection steps are valuable for analytical member manipulation such as Keep Only, Add, Remove, or condition-based selections.

Within classic analyses, Oracle supports creation of selection steps for attribute columns and hierarchical columns . Measure columns can be used to formulate conditions for selection steps, but selection steps aren't directly created for measures themselves.

Selection steps don't replace filters; both serve distinct analytical purposes. They also aren't restricted to pivot tables.

Therefore, C and D correctly identify their applicable column types and their post-aggregation effect on displayed members.

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

A Trellis View is the most appropriate visualization for comparing the same measure across multiple dimensional categories. A trellis displays a series of related visualizations in a grid, allowing users to compare equivalent graphical structures across dimension members.

For example, the designer could use Region or Product Category as an outer-edge dimension and Quarter or another analytical dimension within the repeated visualizations. Because every trellis cell follows a consistent graphical framework, differences in sales performance become easier to identify across categories.

Oracle distinguishes between Simple Trellis and Advanced Trellis use cases. Oracle recommends Simple Trellis for general comparisons and Advanced Trellis when analyzing trends. The documentation also advises controlling dimensional density so that each repeated graph remains readable.

A Narrative View renders textual descriptions generated from query results and isn't optimized for comparative multidimensional visualization. A static table can present all values but provides less immediate visual comparison. A KPI is generally intended to summarize performance against targets rather than display a repeated multidimensional comparison across Region, Product Category, and Quarter.

Therefore, Trellis View best satisfies the scenario.

Reference Topic: Managing and Creating Analyses, Views, and Content — Trellis Views

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

A semantic model with shared business definitions is the correct mechanism for governed enterprise analytics. Oracle defines the semantic model as a metadata layer that maps underlying physical data sources into logical dimensions, measures, hierarchies, relationships, calculations, and presentation objects that reflect how the organization understands its business. This enables centrally defined measures such as Revenue to be calculated consistently regardless of which analyst, dashboard, or analysis consumes them.

After deployment, the semantic model is exposed to users through subject areas . Analysts can create analyses and dashboards using business-friendly objects without needing to understand physical schemas or reproduce calculation logic independently. Centralizing Revenue logic also reduces discrepancies caused by users implementing different spreadsheet formulas or workbook-specific calculations.

CSV files, personal formulas, and independently maintained workbook calculations are useful for self-service scenarios but don't provide the same level of semantic governance, consistency, security, or reusable enterprise definitions.

Therefore, option A directly satisfies the requirement for a trusted and consistently calculated Revenue metric across departments.

Reference Topic: Understanding Oracle Analytics Cloud — Semantic Models and Governed Analytics

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