Free 1Z0-1079-26 Practice Test Questions and Answers (2026)

The "Show Routing Options" action in Oracle Transportation Management (OTM) is an interactive planning tool used during order release execution. Instead of automatically building a shipment using the least-cost or optimal algorithm, this method evaluates all feasible routing possibilities and presents them in a selection grid. Planners utilize this feature specifically when they need manual control over the shipment's execution path. By reviewing the generated list, a planner can explicitly specify the exact itinerary they want the shipment to follow and select the specific carrier (Service Provider) they want to receive the tender, effectively overriding OTM's default automated selection.

Option A: While it displays options, its primary utility is to actively select and execute a plan, not merely to view recommendations without planning.
Option B: Delivery constraints on an Order Base are managed at the order management level, not overridden via the shipment routing options action.
Option C: Auto-tendering is configured via automation agents or parameter settings (e.g., Auto Tender flag), not by using the interactive Show Routing Options screen.

1. Oracle Corporation. (2023). Oracle Transportation Management Cloud Documentation, Release 23C. "Order Management: Order Release Actions - Planning". Section: Show Routing Options.

2. Oracle University. (2022). Oracle SCM Cloud: Transportation Management Implementation Courseware. Chapter 5: Shipment Planning and Execution, pp. 112-115.

In Oracle Transportation Management (OTM) Payment Invoice Manager, the "Pass Through" flag is used to bypass standard automated matching and tolerance rule checks during invoice processing. When an invoice is designated as a Pass Through invoice, OTM does not perform the standard freight bill auditing or invoice-to-shipment matching logic against rules like rate tolerances or weight variances. Instead, the system treats the invoice as pre-approved, allowing it to move directly to the APPROVED status for payment processing without triggering match rule holds or exceptions.

A. The Pass Through setting does not alter or add cost lines to the underlying operational shipment details.
B. It does not control financial allocation mechanics or expand invoice amounts beyond entered invoice line items.
D. It does not perform multi-shipment consolidation actions; consolidation is governed by invoice consolidation rules.

1. Oracle Transportation Management Online Help, Release 24C, "Invoices and Payment Management: Pass Through Invoices."

2. Oracle Supply Chain Management Cloud Documentation: "Invoice Matching and Approval Mechanics in OTM."

In Oracle Global Trade Management (GTM) and Oracle Transportation Management (OTM), regions define specific geographic areas used for compliance, routing, and screening. When a user creates a region directly through the User Interface (UI), the system automatically formulates the region upon saving, making it immediately available for use in business logic and spatial calculations. Conversely, when regions are imported in bulk using a CSV file, the system bypasses this automatic formulation to optimize upload performance. Consequently, CSV-uploaded regions cannot be used directly; administrators must manually run the "Formulate Region" action or schedule a background process to formulate them before they become active and usable within GTM workflows.

A: Incorrect because the GTM application automatically formulates regions created via the UI immediately upon saving, requiring no additional manual formulation steps from the user. E: Incorrect because CSV uploads intentionally bypass automatic formulation for performance reasons, meaning the uploaded regions remain unusable until explicitly formulated by an administrator.

1. Oracle Corporation. (2023). Oracle Transportation and Global Trade Management Cloud Help 23C. "Master Data: Regions - Formulate Region". (Details the automatic formulation via UI and the requirement to manually formulate CSV uploads).

2. Oracle Corporation. (2023). Oracle Global Trade Management Cloud: Implementing Global Trade Management. "Geographic Data and Regions" section. (Specifies the data loading prerequisites and region formulation processes for bulk CSV integrations).

When configuring a Declaration Type in Global Trade Management (GTM) to meet specific customs authority requirements, three key administrative processes must be established. First, a data configuration must be set up to specify which data fields are copied from the Trade Transaction onto the Declaration. Second, a constraint set containing grouping criteria must be defined to determine how multiple Trade Transactions are logically combined into a single Declaration. Third, aggregation criteria need to be created to consolidate individual Transaction Lines into fewer aggregated lines on the final Customs Declaration, based on line attributes such as tariff codes or country of origin. These steps ensure compliance with local customs electronic filing formats.

A: License codes and decrementing logic are configured within Compliance Rule Management for trade license determination, not within Declaration Type setup for customs declaration generation.

- Oracle Cloud Logistics Documentation: Oracle Global Trade Management Process Management Guide

Section "Customs Management: Declaration Types and Data Configuration".

- Oracle Global Trade Management User Guide

Release 24C

Chapter "Declarations and Customs Filing Configuration".

Global Trade Management (GTM) provides flexible methods for populating and maintaining Item Master records to accommodate multi-system enterprise architectures. Items can be automatically integrated from upstream enterprise resource planning systems such as Oracle ERP Cloud via standard integration interfaces (XML or REST APIs). Additionally, business users can manually create and edit Item records directly within the GTM user interface for ad-hoc compliance requirements. Furthermore, bulk creation and batch processing of Item master data can be accomplished using the native CSV upload capability in GTM. These options give organizations flexibility when synchronizing product data across multiple legacy systems into GTM for trade compliance screening and classification.

D: The Product Classification Template is designed specifically for uploading item classification codes to existing items, not for creating new item records. E: External Content Providers supply regulatory data such as tariff rates and restricted party lists, not company-specific Item Master records.

1. Oracle Global Trade Management User Guide, "Item Master Management and Integration Options".

2. Oracle Global Trade Management Integration Guide, "Inbound Data Interfaces for Master Data".

In Oracle Transportation Management (OTM), multi-domain security models strictly isolate data across distinct operational domains to maintain data integrity and tenant confidentiality. To enable a user or user role to access, view, or process transactional data located in a domain other than their primary home domain, administrative setup requires the configuration of Domain Grants. Domain Grants explicitly define cross-domain visibility permissions, enabling authorized users from a central logistics domain to view and interact with data in specified child or client domains. This standard administrative mechanism ensures that cross-domain access is granularly controlled, audited, and systematically maintained.

Option A is incorrect because User Preferences control user interface display defaults and layout settings, not cross-domain data access security. Option C is incorrect because VPD profiles define row-level data filtering within authorized domains rather than granting cross-domain authorizations. Option D is incorrect because Access Control Lists (ACLs) grant permissions to user interface menu items and functional actions, not domain data visibility.

1. Oracle Transportation Management Security Guide

Release 24c

"Domain Security and Access Management: Domain Grants Setup"

Section 3: User Access Controls.

2. Oracle Cloud Administration Guide for OTM/GTM

"Configuring Cross-Domain Data Access via Domain Grants"

Doc ID 1542109.1.

In Oracle Transportation Management (OTM), the fundamental difference between a BUY shipment and a SELL shipment lies in the financial perspective and the direction of the monetary transaction. A BUY shipment represents the procurement of transportation services from a carrier or logistics service provider, resulting in freight costs and accounts payable. Conversely, a SELL shipment is utilized when an organization, such as a Logistics Service Provider (LSP) or a 3PL, provides transportation services to a client and needs to bill them, generating revenue and accounts receivable. The perspective dictates which rates, itineraries, and financial rules are applied during the planning and settlement processes, ensuring accurate cost calculation for purchasing versus revenue calculation for billing customers.

Option A: The Buy/Sell perspective dictates financial transactions (payable vs. receivable), not whether the physical carrier is a third-party entity or a private fleet.
Option B: Both BUY and SELL shipments can be created within the exact same domain; they are not restricted by Company versus 3PLCOMPANY domain structures.
Option C: Buy and Sell perspectives are independent of the physical direction of the goods (inbound vs. outbound); an outbound shipment still requires a BUY shipment to pay the carrier.

1. Oracle Corporation. (2024). Oracle Transportation Management Cloud Release 24A Help Center. "Shipment Management: Shipment Manager." Section: Perspective. This section explicitly defines the Buy perspective as purchasing transportation and the Sell perspective as billing a customer for transportation.

2. Oracle Corporation. (2024). Oracle Transportation Management Cloud Release 24A Help Center. "Financials: Payment and Billing." Section: Overview of Financials. This document details how BUY shipments route to Freight Payment (Accounts Payable) and SELL shipments route to Customer Billing (Accounts Receivable).

The Screen Set Manager in Oracle Transportation Management (OTM) is a core administrative tool used to customize search criteria, define default search values, configure results page columns, and customize action and smartlink menus for standard business object management screens. However, creating multi-panel layouts that integrate multiple distinct visual components, such as interactive tables, geographic maps, and Gantt chart timelines, is configured exclusively through the Workbench Designer and Workbench Layout Manager. Because Screen Set Manager is restricted to managing individual search and result screen displays, it cannot build these complex multi-panel workbench layouts.

A: Customizing results page display columns is a standard configurable feature within the Screen Set Manager. B: Configuring Actions menu options and SmartLinks is natively handled within Screen Set Manager settings. C: Defining default search criteria and default query values is fully supported by the Screen Set Manager.

- Oracle Transportation Management Online Help

"Screen Set Manager Capabilities and Configuration"

Oracle Cloud Logistics Documentation

2026.

- Oracle Transportation Management User Guide

"Configuring User Interface Layouts and Workbenches"

Oracle Help Center

Section 4.2.

In Oracle Transportation Management (OTM), Automation Agents are fundamentally event-driven mechanisms designed to monitor the system. They "listen" for specific business events or conditions to occur (such as an order being created or a shipment being delayed). Once triggered, these agents evaluate predefined conditions and execute a sequence of actions. These actions are highly versatile; they can send automated alerts or notifications to stakeholders, and they possess the capability to create, modify, or delete data objects within the system (e.g., changing a shipment status, assigning a carrier, or building a shipment). This makes them a core component for automating business processes and workflows in OTM.

B: Scheduled executions are managed by the OTM Process Manager or Scheduled Jobs. Automation Agents are event-driven and listen for triggers rather than running on their own built-in schedules. C: This is incorrect because OTM agent actions explicitly include data manipulation capabilities, such as modifying statuses, updating fields, or creating new business objects, alongside sending alerts.

1. Oracle Corporation. (2024). Oracle Transportation Management Help (Release 24A/24B). Section: Business Process Automation > Automation Agents > Agent Manager. This section explicitly defines how agents listen for events and lists the available actions, including data modification and communication triggers.

2. Oracle Corporation. (2023). Oracle Logistics Cloud: Implementing Oracle Transportation Management. Chapter: Configuring Automation Agents. Document details the architecture of event-driven listeners and the execution of data-altering actions versus simple notifications.

In Oracle Transportation Management (OTM), the "Move Order to Existing Shipment" planning action is explicitly designed to manually insert an unassigned order release into an existing shipment. In this scenario, Shipment #10059 is already executing a route (NYC to Philadelphia to Baltimore) and has available capacity. Since order release #1234 picks up in Philadelphia and drops off in Baltimore, using "Move Order to Existing Shipment" allows the dispatcher to explicitly select Shipment #10059 and merge the order release onto it, provided stop sequencing, time windows, and equipment capacity constraints remain valid.

B. Bulk Plan builds new shipments or optimizes across a set, rather than targeting a specific existing shipment directly.
C. Manual creation requires manual shipment construction from scratch rather than merging an order into an active shipment.
D. Show Routing Options generates potential itinerary routes rather than directly assigning the order to an existing shipment ID.

1. Oracle Transportation Management Operational Planning Guide, Release 24C, "Manual Shipment Actions: Move Order to Existing Shipment."

2. Oracle Supply Chain Management Cloud Documentation: "Shipment Management and Order Release Placement."