D is the intended answer among the supplied choices , because Guided Navigation and dashboard-section conditions are designed to display dashboard content conditionally. Oracle Analytics supports associating conditions with dashboard sections so that a section appears only when the configured condition is satisfied. Historically this behavior has been described as Guided Navigation.

However, the question mixes conditional display with role-based authorization . Oracle's current documentation provides an even more direct mechanism for role-specific dashboard visibility: Dashboard Section Permissions . An administrator can grant or deny section access to specific users and application roles. If the strict requirement is “Warehouse Manager role members only,” section permissions are the stronger access-control mechanism.

That option isn't present in the question. Of the choices supplied, Dashboard Prompt is a filtering mechanism, KPI Watchlist monitors performance metrics, and Analysis Filter controls data rather than dashboard-section access. Guided Navigation is therefore the closest and intended examination answer for conditional display.

For production security design, role-based section permissions should be distinguished from merely conditionally rendering content.

Reference Topic: Designing, Creating, and Enhancing Dashboards — Conditional Sections, Guided Navigation, and Permissions

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

Subject Areas provide the business-oriented interface that enables analysts to create governed analyses without writing SQL. Oracle defines subject areas as logical collections of related business information exposed from a deployed semantic model. They contain presentation tables, columns, measures, hierarchies, and other analytical objects that business users can select through the Analysis Editor.

The semantic model hides the complexity of underlying database structures. A user can therefore select concepts such as Customer, Product, Revenue, Quarter, or Region rather than determine physical table names, joins, aggregation rules, or SQL syntax. When an analysis executes, the Oracle Analytics query engine uses the semantic-model metadata to generate the appropriate physical queries against the source systems.

This model combines usability with governance because calculations, relationships, security rules, and business definitions remain centrally managed.

Direct SQL requires technical query knowledge and bypasses much of the business-friendly abstraction the scenario demands. Database triggers serve transactional database functions, while OCI Object Storage is a storage service rather than a semantic reporting interface.

Therefore, Subject Areas are the correct capability for governed, SQL-free business analysis.

Reference Topic: Managing and Creating Analyses, Views, and Content — Subject Areas

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

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

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

Sensitive salary information must be protected through data-level authorization , not merely hidden through visual formatting. The supplied source therefore correctly identifies security applied to the report's data access together with appropriate user or role permissions as the strongest approach.

Oracle Publisher security separates access to functionality, catalog objects, and data sources. Roles can be granted or denied access to particular data sources, while catalog permissions determine who may read or execute report objects. For more granular row-level protection, Publisher can also work with database-enforced mechanisms such as Virtual Private Database policies, as covered elsewhere in the source.

Conditional Formatting is only a presentation mechanism. Hiding a salary column visually doesn't constitute access control if the unauthorized data is still retrieved or otherwise available in report output. Personal Folders restrict catalog sharing but aren't a scalable data-security architecture, and disabling scheduling doesn't affect online access to salary information.

Accordingly, security should be applied at the data-access/data-model layer and reinforced with role-based permissions , making A the correct answer.

Reference Topic: Managing and Securing Oracle Analytics Publisher — Data Access Security and Report Authorization

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

The New option in the Global Header is the appropriate choice. Oracle Analytics Publisher provides global navigation controls so that users can initiate creation tasks without first returning to the Home page. From the global header, selecting New exposes the available object types that the user's privileges permit them to create, such as reports and other Publisher artifacts.

Oracle's current Oracle Analytics Cloud Publisher documentation specifically identifies the global-header workflow for report creation: from the Global Header, click New , then select Report . Similar creation workflows use the same New entry point for other supported Publisher content.

The Catalog option is intended for navigating and managing stored catalog objects rather than immediately initiating a new-object workflow. Home returns the author to the main landing page, which contradicts the requirement to remain within the existing workspace. Open is used for accessing existing content rather than creating a new object. Signed In As relates to account and user-session functionality.

Therefore, New is the global action designed to start creation directly from the current task context and avoids unnecessary navigation back through the Home page.

Reference Topic: Oracle Analytics Publisher — Global Header, Catalog Navigation, and Object Creation

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

An RTF Subtemplate is designed specifically to centralize reusable report-layout content. Oracle defines a subtemplate as formatting functionality that can be defined once and then reused either multiple times within one layout or across multiple report-layout templates.

Common subtemplate use cases explicitly include headers, footers, address blocks, reusable formatting, formulas, and conditional layout structures . In this scenario, the corporate header and footer can be defined once in an RTF subtemplate, uploaded to the Publisher Catalog, and referenced from each report template. When the common content must change—for example, because of branding or legal requirements—the organization can update the reusable subtemplate rather than manually editing dozens of separate RTF templates.

Separate SQL Data Models control report data, not shared presentation content. Catalog folders can organize templates but don't eliminate duplicate header/footer definitions. Dashboard Prompts are unrelated to Publisher document-template reuse.

Oracle's documentation identifies common headers and footers as primary examples of subtemplate usage. Therefore, the maintainable solution is RTF Subtemplates , making D correct.

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

An Action Link Menu is designed specifically for grouping several dashboard actions behind one visible menu. Instead of displaying multiple independent links, the author places an Action Link Menu object on the dashboard and adds the individual action links to that menu. Each contained action can navigate to another analytics object, external web page, or other supported destination.

The Menu Label supplies the text displayed to the user for that grouped menu. Oracle's configuration workflow explicitly instructs authors to enter a value in the Menu Label field and then add individual action links to the Action Link Menu. When the consumer uses the menu, the available actions are presented as selectable options.

Standalone inline or named links would expose multiple separate links and therefore violate the requirement for one visible entry point. The More icon is not the dashboard design mechanism required here, and creating separate dashboard pages introduces unnecessary navigation and maintenance.

Therefore, the correct design is to use an Action Link Menu as the container and configure its Menu Label as the visible menu text.

Reference Topic: Designing, Creating, and Enhancing Dashboards — Action Links and Action Link Menus

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

The author should save the filter as a named filter in the catalog . Oracle Analytics distinguishes between inline filters and named filters. An inline filter belongs to one specific analysis, whereas a named filter is stored independently in the Oracle Analytics Catalog and can subsequently be referenced by multiple compatible analyses.

This is particularly useful for centrally reused business criteria. For example, an organization might create a named filter representing a specific State, Quarter, business unit, or product group. Report authors can then apply that saved filter to multiple analyses rather than recreate the filter definition repeatedly. Oracle also notes that when a named filter is edited and saved, changes can propagate wherever the named filter is referenced, improving consistency and maintainability.

Changing AND/OR grouping merely modifies logical relationships between existing filters and doesn't make the filter independently reusable. Drilling changes the current analytical detail level. A dashboard prompt provides runtime filtering but isn't required simply to reuse the same predetermined filter definition.

Therefore, the appropriate reusable object is a Named Filter saved in the Catalog .

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

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

The recommended Oracle Analytics security model is to manage permissions through Application Roles . An application role represents a set of permissions determining what its members can see and do in Oracle Analytics Cloud. Administrators can assign users, groups, and even other application roles as members, allowing authorization to be administered centrally.

This is considerably more scalable than granting permissions individually. For example, an administrator can create or use an application role for Finance Analysts, assign the required analytics privileges and content permissions to that role, and then add all qualifying users to it. When staffing changes occur, administrators modify membership rather than repeatedly redesigning permissions.

Oracle's current guidance explicitly states that it is a best practice to assign permissions through application roles. Predefined roles such as BI Content Author and BI Consumer provide standard capabilities, while user-defined application roles can be created for organization-specific requirements.

Separate catalogs and duplicate dashboards would create unnecessary management overhead. Database accounts don't replace Oracle Analytics application-layer authorization.

Therefore, assigning users to Application Roles is the correct scalable approach.

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

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

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

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