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

The Autonomous Data Warehouse wallet is obtained from the Oracle Cloud Infrastructure Console , not generated by SQL Developer. The administrator or authorized user first navigates to the appropriate compartment and selects the Autonomous Database instance. From the database details, the Database Connection function provides access to client credentials.

Oracle's current procedure then requires selecting the appropriate wallet type and choosing Download Wallet . A password is supplied and confirmed to protect the downloaded wallet package. The resulting ZIP file contains the secure client credentials and network configuration needed by supported database clients.

SQL Developer uses the wallet only after it has been downloaded. Selecting a service name therefore belongs to the subsequent database-connection process rather than wallet retrieval. Running SQL Developer doesn't need to precede access to the OCI database details, and an independently downloaded JDBC driver isn't a prerequisite for obtaining the wallet.

The terminology in option D uses the older DB Connection label, while current OCI documentation generally uses Database connection , but the workflow remains the same. Therefore, B and D are correct.

Reference Topic: Connecting to Data Sources — Autonomous Data Warehouse Client Credentials and Wallets

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

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

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

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

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

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

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

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

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

Publisher database connectivity is administered through the Publisher Administration page , not through individual reports or dashboards. In an integrated Oracle Analytics environment, Oracle documents the navigation path through Administration → Manage Publisher to reach the Publisher administration interface.

From there, the administrator uses the JDBC Connection option under Data Sources and selects Add Data Source . The JDBC definition contains configuration such as the data source name, database driver, connection string, authentication credentials, optional proxy authentication, and allowed roles. Once configured successfully, that connection becomes available to authorized Data Model developers when they create SQL Query data sets.

A report layout is downstream of data acquisition and therefore isn't required to establish connectivity. Sample data likewise depends on an executable data model. Dashboard Editor manages dashboard presentation rather than Publisher database connections, while the Catalog stores Publisher objects but isn't the administrative interface for defining JDBC infrastructure.

Consequently, the correct workflow is to access Manage Publisher/Publisher Administration and then create the connection through JDBC Connection under Data Sources .

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

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

For device delivery, Oracle Analytics distinguishes between Active Delivery Profile and Specific Devices . Active Delivery Profile lets each user determine delivery behavior through personal delivery preferences. When the Agent must instead target explicitly chosen device types, the author selects Specific Devices and identifies the permitted devices. This satisfies the requirement to avoid reliance on the user's active profile.

For cache seeding, Oracle documents a dedicated Agent workflow. After choosing the analysis or dashboard page and establishing recipients, the administrator clears ordinary user destinations and selects the Analytics Server/BI Server Cache destination. Scheduled execution then populates the query cache using the results generated by the Agent.

The terminology in the question uses Oracle BI Server Cache , while current Oracle Analytics Server documentation refers to Oracle Analytics Server Cache ; functionally, this is the same cache-seeding destination represented by option E.

Selecting Never wouldn't schedule cache seeding. Home Page and Dashboard creates analytics alerts rather than restricting delivery to email devices. Active Delivery Profile does the opposite of the requirement, and Printer isn't the standard cache-seeding destination.

Therefore, the correct selections are Specific Devices and Oracle BI Server Cache .

Reference Topic: Managing Administration, Security, and Performance — Agent Destinations and Cache Seeding

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

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

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

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

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

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

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

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

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

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

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

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

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

A Top N selection/filtering operation is the feature designed to retain only the highest-performing members according to a selected measure. In this case, Product Category is the dimension and current-quarter Sales is the measure used to rank the categories. Configuring the analytical selection to retain the top five categories produces exactly the required comparison population.

Oracle Analytics supports both selection-step member refinement and explicit Top/Bottom N filtering capabilities. The current Oracle Analytics documentation includes Top N examples that identify the highest attribute values based on a measure, which is precisely the analytical pattern in this question.

The important concept is that the ranking is based on the measure rather than visual styling. Conditional Formatting could visually distinguish high or low Sales values but wouldn't restrict the result to five product categories. Repository Initialization Blocks initialize semantic-model variables and have no role in ranking members. Dashboard Page Style controls appearance and layout rather than result membership.

Therefore, Selection Step with Top N filtering is the best supplied answer because it limits the displayed product categories according to their current-quarter Sales ranking and retains only the five highest performers.

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

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

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

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

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

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

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

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

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

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

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

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

A Semantic Model (Repository) Variable stores a centrally defined value that can be referenced by analyses, dashboards, filters, expressions, and other semantic-model logic. Oracle defines repository variables as values maintained within the semantic model rather than supplied interactively by individual report consumers.

Repository variables can be static or dynamic . A static repository variable retains its configured value until an administrator changes it. A dynamic repository variable is refreshed from data returned by an initialization query. Typical shared values include organizational constants, current reporting periods, or other centrally managed values that should be applied consistently.

Option A instead describes a Presentation Variable, which can be populated by a user's prompt selection. Option B more closely describes a Session Variable, whose value is specific to a user's session and is commonly initialized when the user logs in. Option D doesn't describe repository-variable scope because a repository variable can persist across many analysis executions.

Oracle's current documentation calls these Semantic Model (Repository) Variables , preserving the repository terminology used in Classic Analytics. Therefore, the most accurate description is a centrally managed value reusable across analytical content .

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

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

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 Catalog search supports locating objects when users know only part of an object's name. The Catalog Search field matches objects and folders whose names contain the characters entered, so supplying the full or partial name is sufficient; an exact object name isn't required.

Hidden content requires an additional configuration. Oracle's Presentation Catalog documentation specifically states that users must select Show Hidden Items on the Catalog page header when they want hidden objects included in catalog browsing or search results. Availability of hidden objects can additionally depend on the user's privileges, but assuming the user is authorized, this option exposes them to the search operation.

Read-Only is an object property and doesn't improve searchability. Permissions determine access to an object but aren't a search criterion. Favorites provide a shortcut to previously selected content rather than a comprehensive catalog search. Restricting the search to My Folders could omit relevant Shared Folder content.

Therefore, the correct combination is Show Hidden Items plus a full or partial object-name search .

Reference Topic: Managing Administration, Security, and Performance — Presentation Catalog Search

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

A dashboard prompt can affect an embedded analysis only when the analysis is configured to accept the prompt's value. A protected filter deliberately prevents a dashboard prompt from overriding that filter. Oracle describes protected versus unprotected filters specifically as a mechanism controlling whether dashboard prompt values can determine an analysis's results. Therefore, a protected filter is a direct explanation for one of the non-responsive reports.

The second issue is a mismatch between the prompt column formula and the analysis filter formula . Prompt wiring depends on the relevant column identity and formula being compatible. If the analysis uses a modified formula while the prompt targets another formula, Oracle cannot automatically apply the prompt as intended.

By contrast, an Is Prompted filter is specifically intended to receive a prompt value and is therefore normally part of a working configuration. Cache expiration does not explain selective prompt incompatibility, and simply containing measure columns is not itself the documented cause.

The two failed analyses should therefore be inspected for protected filters and formula mismatches between their filtering expressions and the dashboard prompt.

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

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

The appropriate Catalog control is to set the dashboard object to Read-Only . Oracle Analytics allows administrators—and owners for objects they control—to open a catalog item's Properties and modify its access-related attributes. Oracle specifically gives setting an analytics object to read-only as an example of preventing other users from modifying the content.

This setting addresses the requirement directly because the dashboard remains available for consumption while modifications are restricted according to the object's permissions and ownership configuration. It is therefore preferable to mechanisms that would alter discoverability or content organization without enforcing edit protection.

Adding an object to Favorites merely creates a personal shortcut and has no security effect. Transferring ownership doesn't inherently prevent the new owner or other permitted users from modifying the dashboard. Renaming affects catalog references and naming, not write permissions. Archiving creates an archive representation for migration or backup purposes and doesn't constitute the normal method for protecting an active dashboard against edits.

Thus, the correct procedure is to locate the dashboard in the Catalog, open Properties , and configure the item as Read-Only .

Reference Topic: Managing Administration, Security, and Performance — Catalog Object Properties and Read-Only Content

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

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

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