Oracle Analytics provides explicit content-ownership and catalog-property administration. Authorized users and administrators can change or reassign ownership of catalog content. Oracle's Content Management functionality supports assigning content to another user or, for certain object categories, an application role. Classic Catalog also provides ownership operations for supported reporting content.

Catalog items can additionally be designated Read-Only through their properties. Oracle gives the example of making an analysis read-only so other users can't modify it. Thus, D is directly supported.

By contrast, My Folders is private storage . Current Oracle Analytics documentation states that other analytics users can't access content stored there. Content that must be shared should be saved or moved to Shared Folders and given appropriate access permissions. Different object types aren't required to reside in separate folders, and catalog content can be copied, moved, archived, or unarchived subject to privileges and object capabilities.

Therefore, the Oracle-documented answers are A and D . The uploaded file marks A and C, but C conflicts with current Oracle Analytics documentation on My Folders privacy and is therefore corrected here.

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

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

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

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

The intended administrative function is Manage Sessions . Oracle documents session monitoring as the mechanism for viewing the total number of active sessions and detailed information about currently signed-in users. Available details include the user identifier, browser information, login time, last-access time, and associated query activity.

In current Oracle Analytics Cloud interfaces, this functionality is surfaced through Console → Sessions and Query Logs , where the Sessions section displays the total number of sessions and user details. Earlier and related Oracle Analytics interfaces expose the same capability as Administration → Manage Sessions . Since that is the terminology supplied by the answer options, C is the correct examination response.

Application Roles manage authorization membership rather than active sessions. Save Content with HTML Markup is a specific security privilege controlling whether HTML-bearing content can be saved. Manage Privileges configures functional privileges but doesn't itself provide the active-user session list. Catalog monitoring similarly doesn't answer the requirement to enumerate currently signed-in users.

Therefore, Manage Sessions is the correct functional capability, with Sessions and Query Logs being the current OAC Console presentation of that functionality.

Reference Topic: Managing Administration, Security, and Performance — Monitoring Users and Sessions

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

The required capabilities are both available through Column Properties → Column Format . Custom Headings allows the report author to override the default folder or column heading presented in the analysis. This affects the displayed label without modifying the underlying semantic-model column definition. Oracle also permits variables and formatting to be incorporated into custom heading values where appropriate.

Value Suppression controls how consecutive duplicate values are displayed. When the same attribute value occurs repeatedly in adjacent result rows, suppression can display the value only once instead of repeating it on every row. This improves readability in analyses containing grouped or naturally repetitive dimensional data.

Content Paging concerns result retrieval and rendering rather than headings or duplicates. Fixed Headers keeps headings visible during scrolling but does not rename them. Save as Default has a different purpose and does not directly meet either stated requirement.

Oracle's documentation explicitly associates Custom Headings and Value Suppression with the Column Format tab, directly validating B and C.

Reference Topic: Managing and Creating Analyses, Views, and Content — Column Properties and Column Formatting

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

A BAR file is the archive format used when exporting an Oracle Analytics Cloud snapshot for migration or backup. Oracle's current migration workflow is presented through Console → Snapshots . An administrator takes or selects a snapshot, exports it, and downloads the resulting archive as a file with the .bar extension.

The BAR snapshot can contain Oracle Analytics content and configuration, including catalog artifacts such as analyses and dashboards, semantic-model content, application roles, and other supported environment metadata depending on the snapshot and restore options. The administrator then imports the BAR file into the target OAC environment and restores the required content.

This makes snapshot/BAR migration repeatable and substantially safer than manually rebuilding or copying individual analytical objects. Oracle's current documentation explicitly shows the browser downloading bar_file_name.bar and subsequently importing that snapshot into the target environment.

Excel workbooks aren't environment migration packages. XML templates apply to specific Publisher or metadata scenarios, while SQL scripts can't package Oracle Analytics Catalog content and service configuration.

Therefore, BAR File is correct, with current OAC terminology commonly describing it as an exported snapshot (.bar) .

Reference Topic: Connecting to Data Sources and Migrating Artifacts — OAC Snapshots and BAR Files

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

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

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

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

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

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

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

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

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

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

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

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

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