Creating the PL/SQL policy function alone doesn't activate Virtual Private Database protection. The function must be associated with the database object that requires protection. Oracle uses the DBMS_RLS.ADD_POLICY procedure to attach the VPD policy and its policy function to a table, view, or synonym. Once associated, Oracle Database automatically incorporates the policy predicate whenever relevant SQL accesses that object.

The implementation should then be tested directly at the database layer , using a SQL client such as Oracle SQL Developer. Testing with different application or proxy-user contexts confirms that the predicate returns the intended row subsets before Publisher reporting depends on the security configuration.

Catalog roles don't substitute for VPD because catalog permissions protect report objects rather than rows inside database tables. Creating separate reports for individual users would duplicate content and fail to implement centralized row security. Proxy authentication is often useful with Publisher because it preserves individual identity for database-side security enforcement, so disabling it isn't the appropriate completion step. A database restart isn't normally required after attaching a VPD policy.

Thus, the correct database-side actions are apply the policy to the target table and validate its behavior using a SQL tool .

Reference Topic: Managing and Securing Oracle Analytics Publisher — Implementing and Validating VPD Policies

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

Adding a Calculated Column allows an analysis author to derive a new analytical value from existing columns or expressions without changing the underlying physical source data. The calculation becomes part of the current analytical definition and can be referenced throughout the analysis where supported.

Calculated expressions are useful for metrics such as profit percentage, variance, adjusted revenue, unit price, ratios, and other values derived from existing measures or attributes. This provides flexibility at the content-authoring layer while leaving centrally governed semantic-model objects unchanged.

The scope described in the question is important: the calculation must remain reusable within the current analysis . If the organization needed the metric governed and reusable across many analyses, defining the calculation centrally in the semantic model would normally provide stronger enterprise consistency.

A Dashboard Prompt supplies runtime values and filtering rather than creating calculated metrics. BAR files are migration artifacts and don't constitute an analysis calculation mechanism. Application Roles control authorization and permissions.

Therefore, among the available choices, Adding a Calculated Column is the function that creates the required derived metric in the analysis. The uploaded question explicitly associates this behavior with a calculated column.

Reference Topic: Managing and Creating Analyses, Views, and Content — Calculated Columns and Derived Metrics

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

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

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

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

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

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 Publisher layouts can contain multiple report components within the same layout , allowing different representations of a report's data to be assembled into a single formatted document. The Layout Editor Components pane includes visual and tabular components such as charts, pivot tables, tables, images, and other elements that can be dragged into the report layout.

For this finance-report requirement, the author can place a summary chart near the top, use a pivot table for multidimensional financial analysis, and include a conventional table for transaction-level detail. Layout grids and other layout controls can be used to position these components appropriately within the report.

A Dashboard Prompt is intended for runtime filtering and doesn't construct Publisher layout sections. Repository Variables provide centrally managed values rather than report-design components. Data Gateway supplies remote source connectivity.

Oracle documentation explicitly states that Layout Editor provides a drag-and-drop interface and that its Components pane includes objects such as charts and pivot tables. This architecture supports combining the required presentation elements within one report.

Therefore, C. Multiple layout components within a single report is correct.

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

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

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

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

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 most effective combination is query caching plus an optimized semantic model . Oracle Analytics query caching stores previously generated query results so that compatible subsequent requests can be satisfied without repeatedly executing equivalent SQL against the underlying database. This reduces database workload, network traffic, and analytical response time for frequently repeated requests.

Caching alone, however, is not a substitute for sound semantic-model design. Proper logical relationships, aggregation behavior, source mappings, calculations, and physical connection configurations influence the efficiency of generated queries. Optimizing the model therefore addresses the cost of queries that do reach the source, while caching prevents unnecessary repetition of previously resolved requests.

Oracle also emphasizes that administrators need an appropriate cache-management strategy. Cache entries must be invalidated when source data or semantic-model definitions change so that users don't receive stale results.

Disabling caching increases database load. Duplicate subject areas add administrative complexity without inherently improving performance. Running every analysis every minute can substantially increase processing rather than reduce it.

Therefore, C provides the correct performance architecture: optimize query generation and use caching to avoid unnecessary source executions.

Reference Topic: Managing Administration, Security, and Performance — Query Cache and Semantic Model Performance

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