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

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

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

The Layout Editor is Oracle Analytics Publisher's browser-based visual report-design environment. Oracle describes it as a web-based, WYSIWYG, drag-and-drop tool for creating Publisher layouts without requiring authors to manually write an RTF template or formatting code.

Using Layout Editor, the author can insert and arrange components such as tables, charts, pivot tables, images, text items, and layout grids. Component properties, formatting, grouping, sorting, and other presentation characteristics can then be configured through the graphical interface. Layout Editor-generated XPT layouts support interactive browser viewing and a broad range of output types.

A SQL Worksheet is a database-query development environment and doesn't design Publisher report layouts. Catalog Manager manages analytics catalog content rather than visually designing reports. Data Gateway handles remote data connectivity and has no report-formatting role.

This scenario specifically states that the developer wants formatted output without writing RTF templates or custom code , which precisely matches the purpose of Publisher Layout Editor.

Therefore, A. Layout Editor is the correct selection.

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

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

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

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

Drilling on an attribute column performs what Oracle describes as a filter drill . When the user clicks a drillable attribute value, Oracle adds the next lower level to the displayed analysis and creates a filter corresponding to the member on which the user drilled.

Oracle's documentation states that drilling in an attribute column affects all relevant views. After the value is clicked, a column is added to the analysis and a filter is automatically created and listed on the Criteria tab . This distinguishes attribute-column drilling from drilling in hierarchical columns, where expanding or collapsing hierarchy members generally affects only the particular hierarchy view without creating the same analysis-wide filter drill behavior.

The drill operation therefore modifies the analytical context; the underlying criteria don't simply remain unchanged. Oracle also doesn't automatically save the resulting drill filter as a reusable named filter, nor does a drill operation create a dashboard prompt. Those are separate authoring operations.

Consequently, the specific outcome described by Oracle is exactly option A: drilling an attribute column automatically introduces the corresponding filter and adds the lower-level column to the analysis criteria.

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

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

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

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

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

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

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

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

Oracle Analytics Publisher supports multilingual reporting through its translation framework and XLIFF localization files . XLIFF is the XML Localization Interchange File Format used by Publisher to externalize translatable strings from report templates and other supported Publisher content.

For template translation, Publisher extracts textual elements such as titles, labels, and headings into an XLIFF file. The file can then be translated into French, Japanese, or other languages and uploaded against the appropriate locale. At runtime, Publisher automatically uses the translation corresponding to the selected Report Locale .

This enables the organization to retain a single core report definition and template design rather than maintain separate report definitions for every language. Oracle also supports Catalog Translation for user-interface strings such as report descriptions, parameter names, and display names.

Multiple JDBC connections have no role in report localization. A Dashboard Prompt alone cannot translate report labels, and maintaining independent report definitions would increase duplication and maintenance.

Therefore, the source's Translation Manager with XLIFF localization files represents the correct Publisher localization capability, making A correct.

Reference Topic: Managing Report Scheduling, Data Sources, Administration, and Translations — XLIFF and Multilingual Reporting

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

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

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

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

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

When the objective is to stack separate result sets , the Analysis Editor supports set operations such as UNION, UNION ALL, INTERSECT, and DIFFERENCE . Oracle documents a specific Combine Results function that lets authors create criteria from another subject area and apply a set operator to the two query result sets.

Set operations, however, aren't relational join definitions. They combine compatible result sets and require matching numbers of columns and compatible data types. They don't create primary-key/foreign-key or other semantic relationships between subject areas.

Cross-subject-area relational behavior depends on the semantic model , including common dimensions, facts, and relationships defined for the participating subject areas. Oracle also supports cross-subject-area analyses using conformed dimensions, but those relationships derive from model metadata rather than a join created ad hoc through set-operation syntax.

Dashboard prompts simply provide runtime filtering and don't create data relationships. Likewise, adding a second query doesn't itself define semantic join logic.

Therefore, the accurate distinction is: use set operators when stacking compatible result sets; define and govern actual joins through the semantic model .

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

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

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 appropriate Publisher destination is FTP Delivery . Oracle Analytics Publisher supports FTP as one of its standard scheduled report-output destination types. After an administrator configures the FTP delivery infrastructure, report-job authors can select FTP in the Schedule Report Job page and provide the required destination information.

The FTP destination is intended specifically for transferring generated report output to a remote file server. Oracle's scheduling documentation lists FTP alongside destinations such as Email, Printer, Fax, Content Server, and other configured delivery mechanisms. Authentication information such as a valid user name and password is required when defining the FTP destination.

This means a successfully generated PDF, spreadsheet, text file, or other supported output can be automatically transferred to the designated FTP location as part of the scheduled job workflow.

A Dashboard Prompt only collects runtime filtering selections. Narrative View is an analysis-result presentation format, while an Action Link initiates navigation or other actions from analytical content. None provides scheduled file-transfer delivery.

Therefore, the correct delivery mechanism for this requirement is A. FTP Delivery .

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

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

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

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

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

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

Action Links provide context-sensitive navigation from one Oracle Analytics object to another. When an action is attached to a column value, heading, graph value, or other supported element, the user can invoke the action and navigate to another analysis, dashboard, or external destination. Parameters can be mapped so the target receives contextual information from the source.

In the scenario, the selected Customer ID must follow the user into the detailed customer analysis. Presentation variables are one supported method for maintaining or referencing runtime context in analyses and dashboards, while Action Framework parameter mapping supplies the navigation behavior. Together, these mechanisms allow the target analysis to open already constrained to the relevant customer.

Current Oracle Analytics documentation also describes modern Data Actions as passing context values to target canvases and workbooks, reinforcing the same context-preserving navigation principle.

Repository Variables are centrally managed and not primarily intended for transferring a user's selected customer context. Publisher Bursting creates and distributes personalized documents. Snapshot Migration transfers environment artifacts rather than runtime navigation values.

Therefore, among the available choices, Action Links with Presentation Variables is the correct implementation.

Reference Topic: Designing, Creating, and Enhancing Dashboards — Action Links and Contextual Navigation

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

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

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

Successful authentication proves the user's identity, but it does not automatically authorize access to Publisher catalog content. Oracle explicitly distinguishes authentication from authorization: after a user is authenticated, access to Publisher resources is controlled through application-role mappings, permission grants, catalog permissions, and associated security policies.

Following migration, the administrator should therefore verify that users or groups are correctly mapped to the expected application roles and that those roles retain the necessary catalog permissions on the shared Publisher folders, reports, data models, and any dependent catalog objects. Oracle notes that a role with functional Publisher privileges still can't act on catalog objects until the corresponding catalog permissions are granted.

Database optimizer statistics might affect query performance but wouldn't normally produce a Publisher authorization error. Dashboard layout controls presentation, and browser caching doesn't determine application-role authorization.

The uploaded source's own explanation confirms this authentication-versus-authorization distinction, although its extracted Correct Answer marker is displaced. Oracle documentation independently confirms that Catalog permissions and application role assignments are the first security area to inspect.

Reference Topic: Managing and Securing Oracle Analytics Publisher — Authentication, Authorization, Roles, and Catalog Permissions

Query Builder provides a graphical mechanism for defining relational SQL data sets. When multiple tables are involved, the developer must first establish the logical relationship between them. Typically, this means creating a join using matching columns , such as a parent table's primary key and a child table's corresponding foreign key.

After the tables and relationships are established, the required output fields are selected by choosing the check boxes beside the column names in Query Builder's design interface. Those selected fields become part of the generated SELECT list. Oracle's Query Builder documentation and examples show precisely this pattern: create the relationship between tables, select the desired columns, optionally define conditions and sorting, and then save the generated SQL.

A report definition doesn't need to be created before building the query. Dashboard definitions are unrelated to Publisher SQL Query datasets. Sample-data generation occurs after the query has been defined sufficiently to execute, and parameters are optional rather than prerequisites for creating table relationships.

Accordingly, the two essential query-definition operations are joining the related tables and selecting the required columns , making C and E correct.

Reference Topic: Exploring and Creating Reports and Data Models — Query Builder, Joins, and Column Selection

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

A JDBC Data Source must be configured before Publisher data models can retrieve information from an external relational database through JDBC. Oracle Analytics Publisher separates connection administration from report development. Database connections are first established by an administrator through the Publisher Administration page and are then made available to authorized report and data-model developers.

Oracle Publisher supports direct JDBC connections and connections through a JNDI connection pool. The connection definition contains the information Publisher requires to reach the relational source, including the JDBC driver, connection string, credentials, and applicable role-based access configuration.

Only after a valid data source exists can a developer reliably construct an SQL Query Data Set against that source and use it within a Publisher data model.

Translation Manager performs localization and doesn't create database connectivity. A report layout controls presentation after data has been retrieved. Dashboard Prompts belong to interactive analytical filtering and aren't the foundational relational connection mechanism.

Therefore, the external database connection must be established first as a JDBC Data Source , making option C correct.

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

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

Query Builder is specifically designed to construct SQL queries graphically with minimal requirement for manually written SQL. Within the Publisher Data Model Editor, a developer creating a SQL Query data set can launch Query Builder, browse available database objects, add tables or views to the design area, select columns, define relationships between objects, apply query conditions, inspect the generated SQL, and execute the query to review results.

Oracle describes Query Builder as a mechanism for building SQL queries without coding . Its interface separates object selection from query design and output functions, making it suitable for developers or report authors who understand the required data but do not want to manually construct SQL syntax.

Layout Editor serves a different stage of report development: it controls the visual presentation of the report after data has been retrieved. Catalog Manager is concerned with catalog content rather than SQL construction. The Report Wizard assists with creating reports and layouts but is not the graphical relational query-design tool. Parameter configuration defines runtime input values rather than the complete SQL statement.

Consequently, Query Builder precisely satisfies the requirement for graphical SQL development.

Reference Topic: Exploring and Creating Reports and Data Models in Oracle Analytics Publisher — SQL Query Data Sets and Query Builder

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

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

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

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

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

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

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

The Shuttle buttons are used to transfer data fields between the Available and Selected areas of the Table Wizard. During table construction, Template Builder presents the fields available from the loaded report data. The designer selects the required fields and uses the directional shuttle controls to move those fields into the collection that will become columns in the generated table.

This interface pattern lets the designer explicitly determine which elements appear in the table and often also provides controls to reorder selected fields before the table structure is generated. It avoids the need to manually construct every table cell and Publisher field mapping.

Group Above concerns grouping the resulting data rather than initially selecting the table's columns. Sort By determines ordering of records after the relevant fields are selected. Preview allows the author to inspect generated output and isn't used to transfer fields. Word Properties relates to Microsoft Word document behavior rather than Table Wizard field selection.

The uploaded course material also identifies Shuttle buttons as the correct control for moving fields between Available and Selected lists. Consequently, option C is the direct functional match.

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

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