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

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

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

A view is a visual representation of the results returned by an Oracle Analytics analysis. After criteria determine the columns, filters, calculations, and query logic, views control how those analytical results are presented to the consumer. A single analysis can therefore expose the same underlying query results through several different representations.

Oracle Analytics supports views such as tables, pivot tables, graphs, trellises, gauges, narratives, performance tiles, and other visualization types. This separation between analysis criteria and presentation allows authors to choose the most appropriate representation without rebuilding the underlying analytical query.

Views do not define the original attributes selected for the analysis; that occurs through the Criteria tab and Selected Columns. They also do not automatically activate subtotals for every analysis. Totals are explicitly configured where required. Conditional formatting is a separate presentation capability, while dashboard prompts are independently created filtering objects.

Oracle defines a view as a visual representation of analysis results and states that additional views can be added to visualize the same data in different ways. Therefore, option C precisely expresses the architectural purpose of views.

Reference Topic: Managing and Creating Analyses, Views, and Content — Analysis Views

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

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 BIN function is specifically designed to classify a numeric expression into a defined number of equal-width buckets. Oracle documents syntax in which a numeric expression is evaluated at a specified grain using the BY clause, followed by INTO n BINS. The function can return the bin number or one of the interval boundary values , making it appropriate when the analysis needs both dynamic bucketing and a usable representation of each bucket.

In this scenario, Revenue is the numeric measure, while item type and Per-Year-Month establish the required analytical grain. Specifying four bins therefore partitions Revenue values into four dynamically calculated ranges at that grain.

MSUM calculates a moving sum across rows; it doesn't classify values into buckets. PERIODROLLING performs time-series aggregation over a specified period. RANK returns relative ordering, while TOPN identifies the highest-ranked members. None of these functions creates equal-width numeric bins.

Therefore, BIN applied to Revenue at the required grain and configured for four bins directly satisfies the requirement. Oracle's function reference explicitly defines BIN for this purpose.

Reference Topic: Formatting Data and Managing Filters, Selection Steps, and Variables — Analysis Functions and BIN

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

The author should save and run the dashboard to inspect the actual consumer-facing behavior. Dashboard Builder's Preview function is designed primarily to preview the current dashboard page during authoring and doesn't always reproduce the complete navigation experience of the executed dashboard.

Oracle distinguishes the authoring workflow from runtime execution: authors can Preview the current page, Save their changes, or select Run to leave Dashboard Builder and display the dashboard as consumers see it. In the executed dashboard, multiple pages are navigated using page tabs across the dashboard viewer. Therefore, running the saved dashboard is the appropriate validation method when the concern is whether multiple dashboard-page tabs appear correctly.

Dashboard Report Links control items such as Print or Export links associated with dashboard content; they don't create dashboard-page tabs. Section Properties affect the layout and behavior of a section rather than dashboard-level navigation. Deleting and recreating the page as a subpage isn't required, and browser-cache clearing doesn't address the distinction between page Preview and dashboard runtime.

Therefore, option C correctly verifies the end-user experience.

Reference Topic: Designing, Creating, and Enhancing Dashboards — Dashboard Pages, Preview, and Runtime Navigation

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

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

Action Links provide context-sensitive navigation and action execution within Oracle Analytics. They can navigate to BI content, open external web resources, or invoke other supported actions. Presentation variables can participate in navigation scenarios so that contextual values captured at runtime can be supplied when moving between analytical content.

Oracle also explicitly supports conditional Action Links . When an action link is associated with an analysis column, its availability can be controlled by one or more conditions. For example, an escalation action could appear only when Revenue falls below a specified threshold. Oracle documentation describes this as conditionally enabling or displaying the action link according to data-driven criteria.

The remaining statements impose restrictions that do not exist. Action destinations are not limited merely because analyses reside in different catalog folders. Action Links are not restricted to analyses based on one subject area and certainly are not limited to dashboard prompts. Oracle explicitly supports navigation actions that open web pages and other external resources.

Consequently, B and C describe supported Action Link capabilities: runtime contextual navigation and conditional availability.

Reference Topic: Designing, Creating, and Enhancing Dashboards — Action Framework and Conditional Action Links

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

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

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

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

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

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

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

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

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

Oracle Analytics Agents separate the execution condition from the content to be delivered . The Condition tab determines whether the agent should execute. The author can create a new condition or browse to an existing condition based on an analysis. For a condition based on an analysis, Oracle evaluates whether the analysis returns results that satisfy the configured criteria.

The actual payload is configured independently on the Delivery Content tab . Here, the author selects the analysis or dashboard page to deliver and specifies parameters such as subject, output format, and whether results are delivered directly, as an attachment, or as a link where supported.

The Destinations tab determines where content is sent, not whether the condition evaluates to true. The current Oracle documentation identifies the Actions tab as reserved rather than as the location for row-count conditions. The Recipients tab identifies users, application roles, or email recipients but doesn't determine the report output itself. Dashboard prompts are interactive filtering controls, not Agent execution triggers.

Therefore, the required configuration is Condition tab for conditional execution plus Delivery Content tab for the actual analytical content .

Reference Topic: Managing Administration, Security, and Performance — Agents, Conditions, and Delivery Content

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

A “Subject Area not found” condition points first to the analytical metadata layer rather than to dashboard rendering. Analyses reference subject areas exposed by the deployed semantic model. If the expected semantic model wasn't migrated or deployed correctly, if the relevant presentation subject area is missing, or if its name/mapping no longer matches what the analysis references, the dashboard itself can open while individual analyses fail.

Oracle's OAC migration workflow explicitly treats the Data Model and Subject Areas as snapshot components. During certain migration procedures, administrators may deliberately exclude these components from snapshot restoration and separately upload an updated semantic model. This makes verification of the deployed semantic model and its exposed subject areas a critical production-validation step.

Browser compatibility does not create or remove subject-area metadata. Email configuration applies to delivery, and Publisher Runtime Configuration controls report-processing behavior rather than Classic Analysis subject-area resolution.

Therefore, the administrator should first verify that the expected semantic model is deployed and the referenced subject areas and mappings exist correctly , making B the technically supported response.

Reference Topic: Connecting to Data Sources and Migrating Artifacts — Semantic Model and Subject Area Migration

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

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

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

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

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

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

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

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

A shared Dashboard Prompt with Presentation Variables centralizes user input and allows multiple dashboard analyses to reference the same runtime selection. Oracle defines a Presentation Variable as a variable populated through a dashboard column prompt or variable prompt. Each time the user changes the prompt selection, the presentation variable is assigned the selected value or values.

Analyses on the dashboard can then reference the variable in filters, expressions, titles, or other supported locations. This allows a department, fiscal period, region, or comparable filter criterion to be selected once and reused across multiple dashboard components.

The architecture substantially improves maintainability because the dashboard-level interaction is managed centrally rather than requiring a separate prompt or manually maintained filter mechanism for every analysis. Independent prompts would recreate the exact maintenance problem stated in the scenario. Conditional Formatting changes visual presentation rather than providing shared filtering, while exporting analyses creates static outputs and eliminates the interactive dashboard experience.

Therefore, the correct design is A. Use a shared Dashboard Prompt with Presentation Variables .

Reference Topic: Designing, Creating, and Enhancing Dashboards — Dashboard Prompts and Presentation Variables

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

Oracle provides a specific Dashboard Builder procedure for displaying a list of briefing books . The briefing books should be stored in a catalog folder. The dashboard author then drags a Folder object from the Dashboard Objects pane into the required dashboard section and opens its properties. In Folder Properties , the author specifies the folder containing the briefing books.

At runtime, the Folder object presents the folder's available briefing books to authorized users. Oracle also allows the author to control whether the folder initially appears expanded.

The Add to Briefing Book option performs the opposite task: it adds dashboard-page or analysis content into a briefing book rather than displaying a collection of existing briefing books. Downloading individual PDF versions likewise doesn't create a dashboard-accessible list. Saved Customizations preserve dashboard state and prompt selections, not catalog-folder contents.

Oracle's documented workflow directly specifies: add a Folder object, open Folder Properties, and identify the folder containing the briefing books. Therefore, option A precisely implements the required dashboard behavior.

Reference Topic: Designing, Creating, and Enhancing Dashboards — Briefing Books and Folder Objects

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

A List of Values (LOV) mechanism and a Date parameter provide the appropriate controls for this requirement. For sales region, users should select from a predefined, controlled collection of valid business values rather than entering arbitrary text. In Publisher, this is normally implemented using a Menu parameter associated with an LOV . The LOV can contain fixed values or be populated dynamically through a SQL query, thereby ensuring that the regions presented to users correspond to valid source-data values.

For the specific-date requirement, Publisher provides the Date parameter type. A Date parameter exposes an appropriate date-selection interface and passes a date value to the underlying data set using the configured date datatype and Java date format.

Boolean parameters are intended for true/false-style conditions rather than selecting geographical members. Expression and XML are not the appropriate interactive parameter controls for these requirements. Technically, Oracle terminology treats the LOV as the value source associated with a Menu parameter; therefore, option C represents the intended region-selection mechanism in this question.

Reference Topic: Exploring and Creating Reports and Data Models in Oracle Analytics Publisher — Parameters and Lists of Values

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

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

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

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

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

The Oracle Analytics Catalog serves as the organized repository for analytical content. It stores and manages objects that users create and consume, including analyses, dashboards, prompts, Publisher reports, data models, templates, and related analytics artifacts. Content is organized into folder structures and governed through object-level access permissions.

Oracle distinguishes between personal and shared catalog locations. My Folders contains content belonging to an individual user, while Shared Folders contains objects intended to be accessible to authorized users or groups. The Catalog also supports operations such as searching for content, assigning permissions, moving or copying objects, and—in Publisher scenarios—uploading, downloading, and managing translations.

The Catalog isn't a relational database repository and therefore doesn't store database indexes or physical database schemas as its core purpose. It also doesn't generate warehouse tables or replace Oracle Database security. Database-level access control remains separate from analytics-content authorization.

Consequently, option B accurately describes the Catalog as the central organizational and management facility for Oracle Analytics content.

Reference Topic: Understanding Oracle Analytics Cloud — Catalog and Analytics Content Management

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

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

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