1z0-1177-26 Questions and Answers

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

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

The Layout Editor is Oracle Analytics Publisher's browser-based visual report-design environment. Oracle describes it as a web-based, WYSIWYG, drag-and-drop tool for creating Publisher layouts without requiring authors to manually write an RTF template or formatting code.

Using Layout Editor, the author can insert and arrange components such as tables, charts, pivot tables, images, text items, and layout grids. Component properties, formatting, grouping, sorting, and other presentation characteristics can then be configured through the graphical interface. Layout Editor-generated XPT layouts support interactive browser viewing and a broad range of output types.

A SQL Worksheet is a database-query development environment and doesn't design Publisher report layouts. Catalog Manager manages analytics catalog content rather than visually designing reports. Data Gateway handles remote data connectivity and has no report-formatting role.

This scenario specifically states that the developer wants formatted output without writing RTF templates or custom code , which precisely matches the purpose of Publisher Layout Editor.

Therefore, A. Layout Editor is the correct selection.

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

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

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

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

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

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

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

Compound Layout is the correct answer. Oracle Analytics defines a Compound Layout as a collection of multiple views of an analysis displayed together. Authors can position tables, pivot tables, graphs, narrative views, and other views within the same results layout. Oracle specifically states that multiple views can be combined and positioned anywhere within the Compound Layout.

This directly matches a requirement to show executive summary information, trend visualizations, and supporting detail together. An author can combine the relevant views and arrange them so consumers see different perspectives of the same analytical result set without moving between separate objects.

Guided Navigation serves a different purpose. It supports conditional navigation or conditionally displayed content based on analytical conditions; it isn't the layout container for simultaneously presenting multiple analytical views. Briefing Books capture dashboard content for offline or distributable consumption, while Action Links enable navigation or actions from analytical content.

The uploaded source contains an internal contradiction here: its answer marker identifies Guided Navigation , but its own explanation describes Compound Layout . Oracle documentation confirms that A is the technically correct answer .

Reference Topic: Managing and Creating Analyses, Views, and Content — Compound Layouts

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

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

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

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

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

A Pivot Table is the correct layout component because Oracle Analytics Publisher specifically defines it as a mechanism for presenting multidimensional information in tabular form. A pivot table can organize dimensions across rows and columns while simultaneously displaying multiple measures in the data region. It also supports subtotals at multiple hierarchy levels, making it appropriate for analytical reports where users need to compare measures across several dimensional intersections.

A Layout Grid is primarily a structural container used to position report components; it does not itself perform multidimensional analysis. A Gauge visualizes a measure relative to a scale or threshold and is unsuitable for displaying multiple dimensions in tabular form. Text Items provide static or dynamically generated textual information, while Lists are designed for repeated structured content rather than multidimensional cross-tabulation.

Oracle’s Publisher documentation explicitly describes the Pivot Table as providing multidimensional data in tabular form and supporting multiple measures, dimensions, and subtotals at all levels. This directly matches every requirement in the scenario.

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

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

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

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

Oracle Analytics Cloud directly integrates Publisher report content with Classic dashboards . In Dashboard Builder, an author can locate a Publisher report from the Catalog and add it to a dashboard page. Oracle supports placing the Publisher report either as embedded content, where users can view and interact with it directly on the dashboard, or as a link that opens the Publisher report.

When embedded, the report retains Publisher-specific interaction capabilities. Oracle documentation notes that the embedded report toolbar can support operations such as selecting a layout, changing output format, exporting, sending the report to supported destinations, and scheduling the report.

This integration eliminates the need to manually copy generated output into dashboards. Excel exports create detached documents rather than live integrated Publisher content, and FTP is a distribution channel rather than a dashboard integration mechanism.

The uploaded source identifies integration between Publisher catalog content and Oracle Analytics Cloud as the enabling capability, and Oracle's current dashboard documentation explicitly supports adding Publisher reports from the Catalog.

Therefore, the correct answer is D. Integrate Publisher catalog content with Oracle Analytics Cloud .

Reference Topic: Managing and Securing Oracle Analytics Publisher — Publisher and Dashboard Integration

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

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

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

D is the intended answer among the supplied choices , because Guided Navigation and dashboard-section conditions are designed to display dashboard content conditionally. Oracle Analytics supports associating conditions with dashboard sections so that a section appears only when the configured condition is satisfied. Historically this behavior has been described as Guided Navigation.

However, the question mixes conditional display with role-based authorization . Oracle's current documentation provides an even more direct mechanism for role-specific dashboard visibility: Dashboard Section Permissions . An administrator can grant or deny section access to specific users and application roles. If the strict requirement is “Warehouse Manager role members only,” section permissions are the stronger access-control mechanism.

That option isn't present in the question. Of the choices supplied, Dashboard Prompt is a filtering mechanism, KPI Watchlist monitors performance metrics, and Analysis Filter controls data rather than dashboard-section access. Guided Navigation is therefore the closest and intended examination answer for conditional display.

For production security design, role-based section permissions should be distinguished from merely conditionally rendering content.

Reference Topic: Designing, Creating, and Enhancing Dashboards — Conditional Sections, Guided Navigation, and Permissions

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

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

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

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

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

Microsoft Word form fields are a fundamental mechanism used by Oracle Analytics Publisher Template Builder to associate an RTF layout with the report's XML data and Publisher processing instructions. A form field can reference an element from the report data definition so that the associated value is placed dynamically into generated output.

Form fields can also contain BI Publisher processing instructions . For example, Template Builder uses form fields to represent constructs such as for-each processing, grouping, repeating rows, conditional processing, and other layout directives. Oracle's Template Builder configuration documentation specifically describes generating form fields for processing instructions and supports descriptive or abbreviated representations to make the RTF template easier to understand.

Form fields don't eliminate the value of sample XML data; Template Builder uses sample data to expose the available data structure and support previewing. They aren't limited to Word charts, nor are they an Excel-only technology. Option F is directly contrary to their purpose because Publisher commands and processing instructions are precisely what many form fields contain.

Therefore, form fields serve both data-field mapping and layout/processing-instruction embedding , making A and B correct.

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

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

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

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

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

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

When the objective is to stack separate result sets , the Analysis Editor supports set operations such as UNION, UNION ALL, INTERSECT, and DIFFERENCE . Oracle documents a specific Combine Results function that lets authors create criteria from another subject area and apply a set operator to the two query result sets.

Set operations, however, aren't relational join definitions. They combine compatible result sets and require matching numbers of columns and compatible data types. They don't create primary-key/foreign-key or other semantic relationships between subject areas.

Cross-subject-area relational behavior depends on the semantic model , including common dimensions, facts, and relationships defined for the participating subject areas. Oracle also supports cross-subject-area analyses using conformed dimensions, but those relationships derive from model metadata rather than a join created ad hoc through set-operation syntax.

Dashboard prompts simply provide runtime filtering and don't create data relationships. Likewise, adding a second query doesn't itself define semantic join logic.

Therefore, the accurate distinction is: use set operators when stacking compatible result sets; define and govern actual joins through the semantic model .

Reference Topic: Managing and Creating Analyses, Views, and Content — Combining Subject Areas and Set Operations

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

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

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

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

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

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

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

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

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

Oracle Analytics Publisher supports multilingual reporting through its translation framework and XLIFF localization files . XLIFF is the XML Localization Interchange File Format used by Publisher to externalize translatable strings from report templates and other supported Publisher content.

For template translation, Publisher extracts textual elements such as titles, labels, and headings into an XLIFF file. The file can then be translated into French, Japanese, or other languages and uploaded against the appropriate locale. At runtime, Publisher automatically uses the translation corresponding to the selected Report Locale .

This enables the organization to retain a single core report definition and template design rather than maintain separate report definitions for every language. Oracle also supports Catalog Translation for user-interface strings such as report descriptions, parameter names, and display names.

Multiple JDBC connections have no role in report localization. A Dashboard Prompt alone cannot translate report labels, and maintaining independent report definitions would increase duplication and maintenance.

Therefore, the source's Translation Manager with XLIFF localization files represents the correct Publisher localization capability, making A correct.

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

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

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

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

Publisher bursting depends on the bursting delivery query to supply the information needed to format and distribute every split report segment. Oracle states that the delivery query returns a mapping containing elements such as the bursting key, template, locale, output format, delivery channel, output name, and channel-specific parameters.

For email delivery, the recipient email address is supplied through the delivery parameters returned by this query. Oracle's own invoice bursting example retrieves CST_EMAIL_ADDRESS from the customer table and places it in the appropriate email parameter. If the query doesn't return a valid email address for a particular bursting key, Publisher lacks the required destination information for that recipient.

The presence of a chart has no bearing on email delivery. Dashboard prompts are unrelated to scheduled bursting, and query caching doesn't supply recipient addresses.

Therefore, when specific recipients are missing email addresses in the bursting-query results, the failure is attributable to incomplete or invalid delivery information in the bursting control query , making B correct.

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

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