Practice Free 1z0-1177-26 Governed Analytics Professional with Oracle Analytics Cloud Exam Questions Answers With Explanation

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

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

Data Gateway is Oracle Analytics Cloud's supported remote-data-connectivity mechanism for accessing eligible on-premises data sources when the data remains within the organization's network. Oracle instructs administrators to install Data Gateway on a host within the network where the data source resides and register it with the target Oracle Analytics Cloud environment.

OAC can then route supported analytical requests through the configured remote connectivity mechanism rather than requiring the database itself to be directly exposed through a public internet endpoint. When creating the OAC database connection, the administrator enables Use Remote Data Connectivity so queries can use Data Gateway.

Oracle's current security guidance identifies both Data Gateway and Private Access Channel as secure approaches for connecting OAC to on-premises data sources. Since Private Access Channel isn't one of the answer choices, Data Gateway is unequivocally the correct response here.

OCI Object Storage is an object-storage platform and doesn't provide the required database-query bridge. FTP transfers files rather than establishing analytical SQL connectivity. A Public REST Endpoint would contradict the requirement to avoid direct internet exposure.

Therefore, the appropriate feature is Oracle Analytics Data Gateway .

Reference Topic: Connecting to Data Sources and Migrating Artifacts — Data Gateway and Remote Data Connectivity

The recommended architecture is to maintain a single governed dashboard and enforce data visibility through application roles and row-level security in the semantic model . Oracle Analytics allows semantic-model data filters to be assigned to specific application roles. When a user queries an object protected by those filters, Oracle Analytics incorporates the applicable security predicates into the generated query, restricting results to the rows that user's roles are authorized to access.

For example, executives can all open the same Revenue dashboard while a Business Unit data filter automatically restricts each executive to the appropriate organizational data. This approach centralizes dashboard maintenance and security policy while avoiding duplicated content.

Dashboard prompts are useful for interactive filtering, but user-controlled prompts are not a substitute for authorization. Separate dashboards or subject areas for every executive create unnecessary maintenance and introduce the risk of inconsistent logic.

Oracle specifically recommends applying data filters to application roles rather than individual users for scalable row-level security. Therefore, C is the correct governed implementation.

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

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

A Publisher subtemplate is specifically intended to centralize reusable layout and processing components so that they can be referenced from multiple report templates. Oracle defines a subtemplate as formatting functionality that is created once and reused either multiple times in one layout or across multiple report-layout files.

Common Oracle-documented use cases include reusable headers, footers, address blocks, conditional layouts, calculations, and formatting logic . Corporate branding and standard legal disclaimers fit this design precisely. The developer can create an RTF subtemplate containing the standardized components, upload it as a Sub Template object in the Publisher Catalog, and then import and call the required template sections from individual RTF layouts.

If company branding or legal language changes, updating the centralized subtemplate minimizes maintenance across all reports that reference it.

Duplicating the content in every RTF layout creates consistency and maintenance problems. Separate layouts still duplicate common material. SQL data models should represent data retrieval and structure, not presentation branding.

Therefore, C. Create a subtemplate and reference it from report templates is Oracle's recommended reusable-design pattern.

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

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

A Presentation Variable is the variable type specifically designed to capture a value selected by a user through a dashboard prompt and make that value available dynamically to analyses and other dashboard content.

Oracle states that a presentation variable can be created as part of either a column prompt or a variable prompt . Whenever the user selects one or more values in the associated prompt, Oracle sets the presentation variable to the selected value or values. Analyses can then reference that variable in filters, column formulas, titles, narrative text, or other supported expressions.

In this scenario, selecting Fiscal Year at runtime establishes a user-controlled value that multiple analyses can consume. Because the value changes interactively as the user changes the prompt selection, Presentation Variable is the appropriate variable scope.

A Repository Variable is centrally managed and isn't normally populated from a user's dashboard selection. Session variables generally hold user-specific or system values initialized for a login session. Initialization blocks are mechanisms used to populate certain server/session variables rather than the runtime dashboard variable required here.

Therefore, Presentation Variable precisely matches the described prompt-driven dashboard behavior.

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

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

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

Action Links enable context-sensitive navigation from analytical content to related analyses, dashboards, web pages, or other supported targets. An action link can be associated with a column heading, column value, or hierarchy-level value in an analysis. When invoked, the link can pass mapped parameters or contextual information to the destination.

This makes Action Links appropriate for moving from a summarized analytical view into transaction-level detail. For example, a user could select a customer, product, opportunity, or regional value in a summary analysis and open a detailed destination that reflects the selected context. Oracle's Action Framework supports parameter mapping when configuring the target action.

Modern Oracle Analytics workbook Data Actions provide a comparable capability: Analytics Links can pass source-canvas context into another canvas or workbook. The classic Action Link remains the feature explicitly represented in this question.

Repository Variables contain centrally managed values but aren't navigation mechanisms. Runtime Configuration controls Publisher processing settings, and Bursting generates and distributes personalized Publisher documents.

Therefore, B. Action Links is the correct mechanism for contextual navigation from summary to detailed analytical information.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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 correct mechanism is to assign catalog permissions based on application roles . Oracle Analytics Publisher authorization combines functional roles with catalog permissions. A user may possess general Publisher functionality, but access to a particular catalog object still depends on permissions granted for that report and its containing folders.

For this scenario, an HR Manager application role can be granted the required Read and Run Report Online permissions for the payroll-report folder or individual reports. Other authenticated users should not receive those permissions. Oracle recommends role-based administration because managing group or role membership is substantially more scalable and auditable than maintaining permissions individually for every user.

Oracle also emphasizes that roles with functional privileges can't perform catalog actions unless they possess the corresponding catalog permissions. This makes catalog security the correct control point for protecting sensitive payroll reports.

Query caching affects performance rather than authorization. Dashboard Prompts filter runtime values but aren't security boundaries. Separate report layouts change presentation and don't prevent unauthorized execution.

Therefore, C. Assign catalog permissions based on application roles provides the required role-based report access control.

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

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

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

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

Report Bursting is specifically designed to split a single report execution into multiple personalized documents and deliver each document according to recipient-specific information. In this scenario, the finance department can use Customer ID as the bursting Split By and Deliver By key. The bursting delivery query can retrieve each customer's email address, output format, template, locale, and other delivery parameters from the underlying data.

Oracle provides a documented invoice bursting example in which CUSTOMER_ID identifies each report segment, the output format is selected dynamically, the delivery channel is EMAIL, and the customer's email address is supplied by the bursting query. The same architecture permits thousands of invoices to be generated from one report definition and distributed independently.

Layout Editor controls visual report design but doesn't automate recipient-specific splitting. Dashboard Prompts provide runtime filtering, and Conditional Formatting changes presentation according to conditions.

Therefore, Report Bursting precisely satisfies both requirements: generating a separate PDF for each customer and automatically delivering each document to the corresponding email address.

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

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

Runtime Configuration controls Publisher's system-level processing and document-generation behavior. Oracle's Runtime Configuration framework includes settings for different output types, PDF processing and security, FO processing, memory and performance behavior, template processing, report delivery properties, and associated font mappings.

Oracle's runtime configuration file also illustrates settings such as system-temp-dir, PDF compression, PDF security, and font definitions. In the administrative interface, the Runtime Configuration page provides corresponding system-level properties, with some settings also configurable at individual report level. When report-level and system-level settings differ, Oracle can apply the more specific report-level setting where documented.

A Subject Area is a governed analytical data presentation layer and has nothing to do with Publisher document-processing defaults. Presentation Variables capture runtime prompt values. Selection Steps refine displayed members of an analysis.

The uploaded source's explanation explicitly identifies Runtime Configuration as defining system-wide Publisher processing and output-generation behavior. Its extracted “Correct answer” marker is misplaced relative to the options; Oracle documentation confirms that A. Runtime Configuration is the technically correct answer.

Reference Topic: Managing Report Scheduling, Data Sources, Administration, and Translations — Runtime Configuration

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

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

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

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

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

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

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

A and B are the intended answers. Oracle Analytics supports constrained or cascading prompts , where a value selected in one prompt restricts the values presented by another. A classic example is selecting a Region first and having a subsequent City prompt display only cities within that region. This improves usability and prevents invalid combinations of prompt values.

Oracle also allows prompt default selections to be derived from server-side variables. These include session variables , which can contain user-specific information initialized when a user signs in, and semantic-model/repository variables, which provide centrally maintained values. Such variables can therefore initialize prompts dynamically rather than requiring hard-coded default selections.

Statements C and D impose restrictions that Oracle Analytics does not require. F directly contradicts Oracle variable support.

There is an important technical issue with this question: Oracle Analytics also supports different prompt forms, including column and variable prompts, so E can be interpreted as generally valid . Consequently, E is a weak distractor and makes the item somewhat ambiguous when interpreted literally. For the supplied two-answer examination key and the specific concepts being tested—constrained prompts and variable-based defaults— A and B are the intended selections .

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

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

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

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