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

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

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

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

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

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

The appropriate Publisher destination is FTP Delivery . Oracle Analytics Publisher supports FTP as one of its standard scheduled report-output destination types. After an administrator configures the FTP delivery infrastructure, report-job authors can select FTP in the Schedule Report Job page and provide the required destination information.

The FTP destination is intended specifically for transferring generated report output to a remote file server. Oracle's scheduling documentation lists FTP alongside destinations such as Email, Printer, Fax, Content Server, and other configured delivery mechanisms. Authentication information such as a valid user name and password is required when defining the FTP destination.

This means a successfully generated PDF, spreadsheet, text file, or other supported output can be automatically transferred to the designated FTP location as part of the scheduled job workflow.

A Dashboard Prompt only collects runtime filtering selections. Narrative View is an analysis-result presentation format, while an Action Link initiates navigation or other actions from analytical content. None provides scheduled file-transfer delivery.

Therefore, the correct delivery mechanism for this requirement is A. FTP Delivery .

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

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

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

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

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

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

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

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

The recommended architecture is to maintain a single governed dashboard and enforce data visibility through application roles and row-level security in the semantic model . Oracle Analytics allows semantic-model data filters to be assigned to specific application roles. When a user queries an object protected by those filters, Oracle Analytics incorporates the applicable security predicates into the generated query, restricting results to the rows that user's roles are authorized to access.

For example, executives can all open the same Revenue dashboard while a Business Unit data filter automatically restricts each executive to the appropriate organizational data. This approach centralizes dashboard maintenance and security policy while avoiding duplicated content.

Dashboard prompts are useful for interactive filtering, but user-controlled prompts are not a substitute for authorization. Separate dashboards or subject areas for every executive create unnecessary maintenance and introduce the risk of inconsistent logic.

Oracle specifically recommends applying data filters to application roles rather than individual users for scalable row-level security. Therefore, C is the correct governed implementation.

Reference Topic: Managing Administration, Security, and Performance — Application Roles and Row-Level Security

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

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

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

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

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