Report Bursting is specifically designed to split a single report execution into multiple personalized documents and deliver each document according to recipient-specific information. In this scenario, the finance department can use Customer ID as the bursting Split By and Deliver By key. The bursting delivery query can retrieve each customer's email address, output format, template, locale, and other delivery parameters from the underlying data.

Oracle provides a documented invoice bursting example in which CUSTOMER_ID identifies each report segment, the output format is selected dynamically, the delivery channel is EMAIL, and the customer's email address is supplied by the bursting query. The same architecture permits thousands of invoices to be generated from one report definition and distributed independently.

Layout Editor controls visual report design but doesn't automate recipient-specific splitting. Dashboard Prompts provide runtime filtering, and Conditional Formatting changes presentation according to conditions.

Therefore, Report Bursting precisely satisfies both requirements: generating a separate PDF for each customer and automatically delivering each document to the corresponding email address.

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

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

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

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

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 SQL Query Data Set is the appropriate Publisher data-set type when a report data model must retrieve relational data by executing a custom SQL statement. In the Data Model Editor, the developer selects New Dataset → SQL Query , chooses the required configured data source, and then enters a Standard SQL statement or invokes Query Builder to construct the statement graphically.

Oracle Analytics Publisher supports SQL Query Data Sets against Oracle Database and other supported relational sources. The SQL can contain standard SELECT logic and can also be extended with supported bind variables and other Publisher capabilities where required. This gives the developer direct control over the data retrieved for the report.

An XML Data Set consumes XML-based data rather than running relational SQL. An Excel Data Set retrieves spreadsheet content, while generic file-based options don't provide direct execution of a custom Oracle Database SQL statement.

Oracle's official documentation explicitly instructs developers to create an SQL Query dataset for this requirement. Therefore, C directly matches the described data-access method.

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

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

Template Builder for Word is specifically designed for developing sophisticated Oracle Analytics Publisher RTF templates within Microsoft Word . It is installed as a Word add-in and simplifies insertion of Publisher data fields, tables, repeating groups, charts, forms, processing instructions, and other report components.

RTF templates retain access to Microsoft Word's native document-formatting features. This makes them particularly appropriate for reports requiring corporate branding, precisely positioned text, headers and footers, images, complex tables, and other print-oriented formatting. Publisher's RTF processing capabilities additionally support conditional formatting, grouping, dynamic columns, calculations, and other advanced report logic.

Oracle's official documentation identifies Template Builder as an add-in that automates insertion of frequently used Publisher components and provides tools to preview output using sample XML data. The underlying RTF format also supports more complex Publisher processing instructions where required.

Dashboard Builder creates analytical dashboards rather than Word-based templates. SQL Developer is a database-development tool. Catalog editing doesn't provide Word document formatting.

Therefore, Template Builder for Word is the correct tool for this highly formatted RTF reporting requirement.

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

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

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

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

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 correct settings are User Can Refresh Report Data and User Level caching . Oracle Analytics Publisher defines User Level caching as maintaining a separate cache for each user. With this option enabled, the cached data presented to one user comes from that user's private cache rather than a cache shared with other consumers. This is particularly relevant when report results contain user-sensitive or security-filtered information.

The User Can Refresh Report Data property addresses the second requirement. When enabled, Publisher provides the user with the ability to request a refresh from the Report Viewer. Publisher then generates a new data set instead of continuing to use the existing cached copy.

Caching Duration only controls how long cached data remains valid; setting it to zero does not establish user-specific isolation as described in the scenario. Disabling data caching would eliminate the caching requirement altogether rather than maintaining secure per-user caches. Document Caching stores the generated report document—data plus layout—not merely the parameter list. Clearing all caches following every execution would undermine the performance purpose of caching.

Therefore, A provides freshness on demand , while D supplies user-level cache isolation .

Reference Topic: Managing and Securing Oracle Analytics Publisher — Report Properties and Caching

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

Catalog Object Permissions provide the required authorization control for shared Oracle Analytics content. Dashboards, analyses, folders, and related catalog objects can be assigned permissions that determine which users or application roles can read, modify, delete, or otherwise manage them. For this scenario, the administrator can grant the Finance application role appropriate modification privileges while granting other authorized consumers read-only access.

Oracle recommends assigning access through roles rather than individual users wherever possible. This simplifies administration because users inherit the catalog permissions associated with their application-role membership. Shared-folder permissions can also be used so that contained objects inherit a consistent security configuration.

A Dashboard Prompt controls filtering and runtime input, not modification rights. Data Gateway provides connectivity to remote or on-premises sources. Query Cache improves analytical query performance but has no role in dashboard authorization.

The uploaded source identifies Catalog Object Permissions for this scenario, and Oracle documentation confirms that shared analytics content can be secured using permissions assigned to users and roles.

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

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

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

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