Oracle Updated 1z0-1177-26 Exam Questions and Answers by wilf

The two fundamental bursting keys are Split By and Deliver By/Delivery By . The Split By element identifies how the report data is divided into individual blocks. For example, when producing customer invoices, CUSTOMER_ID can be used as the Split By value so that a separate data block and document can be generated for each customer.

The Deliver By element determines how formatting and delivery information is associated with each split segment. Oracle's bursting engine uses this key to correlate each section with information returned by the delivery query, including template, output format, locale, delivery channel, destination, and other delivery parameters. Consequently, different recipients can receive differently formatted outputs through different delivery channels from a single report execution.

Bursting definitions belong to the Publisher data model , not exclusively to the scheduling interface. Bursting is also not restricted to one output format across all generated documents. Supported delivery mechanisms extend beyond FTP and can include email, printers, content repositories, and other configured destinations. The Diagnostic tab is not where the bursting delivery query is conceptually defined.

Thus, Split By controls data segmentation , while Delivery By controls segment-specific formatting and distribution .

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

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

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