The Object Card layout is specifically designed to meet these requirements. Its primary purpose is to display a summary of a business object's attributes, such as a product's name, price, and a brief description, in a visually organized and compact manner. Furthermore, the Object Card is inherently interactive, intended to be used within a collection (like a list of products) where selecting a card navigates the user to a more detailed view of that specific object. This dual function of summarization and navigation makes it the ideal choice for the described scenario.

B. Mini Card: This layout is used to display a single, simple metric or a key value in a very compact form, not for summarizing multiple product attributes.

C. Image Card: This layout prioritizes the display of an image over textual information, making it less suitable for providing a balanced summary of a product's various details.

D. Scoreboard: This is a specialized card for displaying a set of Key Performance Indicators (KPIs) or metrics, not for presenting general, descriptive information about an object like a product.

1. Oracle Visual Builder Documentation

"Cards" Component Overview. The documentation explicitly states the use case for the Object Card: "Use an object card to display a summary of an object's attributes. An object card is often used in a list where each card represents an object and can be selected to navigate to a page with more details about the object." This directly aligns with both requirements in the question. The same source defines the other card types for their more specific use cases (Mini Card for single metrics

Scoreboard for KPIs).

Source: Oracle Help Center

Develop Applications with Oracle Visual Builder

"Work with UI Components" -> "Cards".

2. Oracle Visual Builder Cookbook

"Cards" Pattern. The official Cookbook provides design patterns and usage guidelines. For the Object Card

it demonstrates its use for summarizing an item in a collection and linking to details

reinforcing its suitability.

Source: Oracle Visual Builder Cookbook

Patterns -> Cards. (Accessible via the Oracle Help Center for the specific Visual Builder version).

Oracle Visual Builder Studio (VB Studio) is not automatically provisioned with an Oracle Fusion Cloud Applications tenancy. While customers are entitled to use it, an administrator must perform a one-time, manual setup to create the VB Studio instance. This single instance serves as a centralized development environment that can be configured to connect to and manage extensions for all of the Fusion Cloud Applications environments (e.g., development, test, production) within that tenancy. The provisioning is an explicit action, not an automatic feature.

A. An instance is not automatically provisioned, and the single instance you create is not exclusively mapped to a TEST environment; it can manage all environments.

B. An instance is not automatically provisioned, and the single instance you create is not exclusively mapped to the production environment.

D. You do not get multiple instances automatically. A single VB Studio instance is provisioned manually to manage development across all environments.

1. Oracle Help Center

Administering Oracle Visual Builder Studio. In the section "Set Up Oracle Visual Builder Studio to Extend Oracle Cloud Applications

" the documentation explicitly states

"Before you can start using VB Studio to extend your Oracle Cloud Applications

you must perform a one-time setup to create a VB Studio instance and give your team members access to it." This confirms the manual provisioning step.

2. Oracle Cloud Infrastructure Documentation

Visual Builder Studio. The "Set Up Visual Builder Studio" guide outlines the required steps

with the first step being "Create a VB Studio Instance." This procedural documentation shows that instance creation is a user-initiated task

not an automated part of the tenancy setup.

3. Oracle Help Center

Administering Oracle Visual Builder Studio. The "Typical Workflow for Administering VB Studio" section begins with the prerequisite: "A VB Studio instance is created." This reinforces that the instance must exist before any administrative or development work can begin

implying it is not pre-provisioned.

The "Share" feature in Oracle Visual Builder is specifically designed for this purpose. It allows a developer to create a shareable version of their application directly from their private workspace. This generates a unique URL that can be given to other users, like Troy, for testing and feedback. This action creates a snapshot of the application's current state without requiring the changes to be published or committed to a Git repository, perfectly aligning with Jane's need to get feedback before pushing to Git.

A. By creating a shared workspace with Troy

Workspaces in Visual Builder are private to the user. Collaboration on the source code itself is managed through a shared Git repository, not a "shared workspace" feature.

B. By clicking the Publish button in her workspace

Publishing an application is a formal deployment step that makes it available to end-users in a live environment. This is different from sharing a development version for internal testing.

D. By pushing the changes to a shared branch before pushing it to Git

Pushing changes to a shared branch is, by definition, pushing it to a Git repository. This contradicts the explicit requirement to share the application before pushing to Git.

---

1. Oracle Cloud Documentation for Visual Builder

"Develop Applications with Oracle Visual Builder":

Section: "Share Your Application for Testing"

Content: "You can share your web or mobile application with other users to allow them to test it or to get their feedback. When you share an application

you are essentially creating a version of the application that is based on the current state of your workspace... Sharing an application does not publish it

and it does not affect the data in your development database." This directly supports option C.

Reference: Oracle Help Center: Share Your Application for Testing

2. Oracle Cloud Documentation for Visual Builder

"Develop Applications with Oracle Visual Builder":

Section: "Publishing Your Application"

Content: "When your application is ready for production

you publish it to make it live." This clarifies that "Publish" (Option B) is for production deployment

not for pre-commit testing.

Reference: Oracle Help Center: Publishing Your Application

3. Oracle Cloud Documentation for Visual Builder

"Develop Applications with Oracle Visual Builder":

Section: "Collaborate with Others"

Content: This section details how collaboration on the application's source code is managed using a Git repository

including branching and merging strategies. This confirms that Git (Option D) is the formal collaboration mechanism

distinct from the informal "Share" feature. It also implicitly refutes the concept of a "shared workspace" (Option A).

Reference: Oracle Help Center: Collaborate with Others (Note: A generic link is provided as the exact anchor may vary

but the section on Git collaboration is the key source).

A Guided Process in Oracle Fusion Cloud Service is configured using a checklist template. According to the official Oracle documentation, these processes are designed with specific constraints to ensure system performance and a streamlined user experience. The configuration limits mandate that a Guided Process must contain at least one step to be valid and can scale up to a maximum of 50 steps. Any number of steps outside this range is not supported by the application.

B. Minimum 1 and maximum 10: This is incorrect because the maximum number of steps allowed is 50, not 10.

C. Minimum 4 and maximum 10: This is incorrect as the minimum is 1, not 4, and the maximum is 50, not 10.

D. Minimum 2 and maximum 25: This is incorrect because the minimum required step is 1, not 2, and the maximum is 50, not 25.

1. Oracle Help Center. Implementing Journeys (for Oracle Fusion Cloud HCM

Release 24B). Chapter: Checklist Templates

Section: How You Configure Guided Process Steps.

Quote/Paraphrase: The documentation explicitly states

"A guided process can have a minimum of 1 step and a maximum of 50 steps." This section details the configuration parameters for creating guided processes.

2. Oracle Help Center. Using Checklists (for Oracle Fusion Cloud HCM

Release 24B). Chapter: Checklist Tasks

Section: Guided Process.

Quote/Paraphrase: This section describes the functionality of a Guided Process and its structure

which is built upon checklist templates. The underlying constraints of the template

including the 1-to-50 step limit

govern the Guided Process configuration.

The oj-sp-dashboard-landing-page is a specific Oracle JET component used within Visual Builder to structure dashboard pages. According to the official Oracle JET documentation, which governs Visual Builder components, the page-title attribute is explicitly defined as a required property. This attribute provides the main heading for the page, which is a fundamental element for user interface structure, context, and accessibility. The component's definition mandates its presence for proper rendering and functionality. The other options, such as page-subtitle and in-flow-back, are optional attributes that provide additional descriptive text or control layout behavior but are not essential for the component's instantiation.

B. Page Subtitle: This is an optional string attribute used to display supplementary text under the main title.

C. In Flow Back: This is an optional boolean attribute that controls the layout of the back button; it defaults to false.

D. Primary Action: This refers to an optional named slot, not a required attribute, used for embedding components like buttons.

1. Oracle JET Developer Cookbook: The documentation for the oj-sp-dashboard-landing-page component explicitly lists its attributes. In the attributes table

page-title is marked as "Required".

Source: Oracle JET Cookbook

oj-sp-dashboard-landing-page Component API documentation.

Reference: Under the "Attributes" section for the component

the entry for page-title specifies Required: true. The entries for page-subtitle and in-flow-back specify Required: false. The primary-action is listed under the "Slots" section

which are for content injection and are not required attributes.

Oracle Fusion Cloud Extensions, utilizing Oracle's Platform as a Service (PaaS) capabilities, are specifically designed to enhance business agility. They provide a framework and tools, such as Visual Builder and Oracle Integration, for businesses to rapidly develop and deploy custom functionalities, user interfaces, and integrations. This allows organizations to tailor their Oracle Cloud Applications to meet unique and evolving business requirements without modifying the core application code. By enabling quick adaptation and extension, businesses can respond faster to market changes, streamline processes, and innovate, which is the essence of business agility. This approach also ensures that customizations are preserved during routine application updates.

A. Extensions are intended to streamline and optimize business processes, thereby increasing efficiency, not slowing them down.

B. The PaaS for SaaS extension model is designed to decouple customizations, managing complexity and ensuring core applications remain stable and upgrade-safe.

D. The primary purpose of extensions is to provide flexibility and adaptability, which is the direct opposite of enforcing rigid, unchangeable processes.

1. Oracle Corporation. (2021). A Guide to Extending and Personalizing Oracle Cloud Applications. Solution Brief. Page 2

"Introduction". The document states

"Oracle’s PaaS for SaaS strategy allows you to extend and personalize Oracle Cloud Applications in an agile

cost-effective way that supports your unique business needs."

2. Oracle Corporation. (2022). Extend Oracle Fusion Cloud Applications with Oracle PaaS. White Paper. Page 3

"Innovate Faster". This section details how the platform enables businesses to "quickly respond to changing business needs by rapidly building and deploying new business services."

3. Oracle Help Center. (2024). Overview of Visual Builder in Oracle Integration 3. Section: "Why Use Visual Builder?". The documentation highlights that Visual Builder allows users to "Quickly create and extend applications using a visual

browser-based development environment

" which directly contributes to the speed and agility of adapting applications.

Oracle Redwood is Oracle's proprietary design system and user experience (UX) language. Its primary purpose is to provide a consistent, modern, and intuitive user interface across Oracle's suite of applications. The main advantage of using Redwood is the ability to rapidly develop applications with a high-quality, pre-built, and user-friendly interface. It offers a comprehensive library of components, patterns, and templates designed specifically to enhance usability and provide a superior user experience, which is the core goal of any design system.

A. Real-time data analytics: This is a function of backend databases and analytics services (like Oracle Analytics Cloud), not a primary feature of the Redwood design system, which focuses on the user interface.

B. Integrated machine learning: Machine learning capabilities are provided by specific Oracle Cloud Infrastructure (OCI) AI services or database features, not by the Redwood front-end design system.

D. Cross-platform compatibility: While Redwood components are designed to be responsive and work on various devices, this is a supporting feature. The fundamental advantage is the quality of the user experience itself, which is best described as "user-friendly."

1. Oracle Redwood Official Website: "Redwood is Oracle’s new user experience design language. We created it to help our teams and our customers

partners

and developers quickly build applications that reflect the Oracle brand and our commitment to a superior user experience."

Source: Oracle Corporation. (2024). Redwood Design System. Retrieved from https://redwood.oracle.com/. (Accessed on the homepage).

2. Oracle Cloud Infrastructure Documentation - Visual Builder: "The Redwood design system provides the foundation for the next generation of Oracle applications. It offers a new user experience based on a new set of components and page templates..."

Source: Oracle Help Center. (2024). Get Started with Redwood. In Developing Applications with Oracle Visual Builder. Section: "About the Redwood Design System".

3. Oracle Blog: "Redwood is the name of our new user experience design language... It’s a design system that will scale to our thousands of products and services... to deliver a seamless

unified user experience."

Source: Lam

J. (2019

September 16). The Story of Redwood: Oracle’s New User Experience. Oracle Blogs. Paragraph 2.

Redwood page templates in Oracle Visual Builder are designed for reusability and encapsulation. The components within a template, such as a primary action button, are not directly accessible from the page that uses the template. Instead, the template exposes specific, predefined events. The button inside the template is wired to fire a primaryAction event. To define what this button does, you create an action chain on the page and map it to this primaryAction event exposed by the template. This decouples the page's logic from the template's internal structure, which is a core design principle.

A. You cannot. The functionality is determined by the original template

This is incorrect. Templates are designed to be customized by the pages that consume them; otherwise, they would have very limited utility.

B. Create an onAction action chain on that button

This is incorrect because you cannot directly select or modify components encapsulated within a page template from the page designer's context.

C. Remove the existing button from the template and add your own

This is an improper approach that breaks the connection to the template, defeating the purpose of using it for a consistent layout and future updates.

1. Oracle Visual Builder Documentation - Develop Applications with Oracle Visual Builder: In the section "Work with Page Templates

" the subsection "Add an Event Listener to a Page Based on a Template" explicitly states: "When you create a page from a template

you can add an event listener to the page to trigger an action chain when an event on the template occurs. For example

you can add an event listener that listens for the template's primaryAction event and triggers an action chain to save data." This directly supports answer D.

Source: Oracle Help Center

Develop Applications with Oracle Visual Builder

Release 24.04

Part Number F82535-02

Chapter: "Work with Page Templates".

2. Oracle Visual Builder Documentation - Page Model Reference: The documentation on page templates describes how they define custom events that can be handled by the consuming page. The primaryAction event is a standard event exposed by Redwood templates for this exact purpose. The page's event listener mechanism is the designated way to subscribe to and handle these template events.

Source: Oracle Help Center

Develop Applications with Oracle Visual Builder

Release 24.04

Part Number F82535-02

Chapter: "Understand the Page Model".

The Redwood Design System provides specific components for modal dialog messages, which are designed to interrupt the user's workflow and require an immediate response. The three available dialog message components are oj-sp-message-dialog-general for informational messages, oj-sp-message-dialog-destructive to confirm potentially harmful actions (like deletion), and oj-sp-message-unsaved-changes to prevent accidental data loss when a user attempts to navigate away from a page with unsaved data. These components directly align with the requirement for user interruption and decision-making.

oj-sp-messages-banner: This is a banner component. Banners are non-modal and less intrusive than dialogs; they do not force an immediate user decision.

oj-sp-smart-search-page: This is a page template for building search functionality, not a component for displaying dialog messages.

oj-sp-message-banner-unsaved-changes: This is a banner variant for unsaved changes. Like other banners, it is a non-modal message and does not interrupt the user's workflow.

1. Oracle Visual Builder Documentation

"Use Messaging Patterns": This official guide details the different messaging components in Redwood. It explicitly distinguishes between dialogs and banners

stating

"Use a dialog for critical information that the user must see and act on before continuing." It then lists the three dialog types: General

Destructive

and Unsaved Changes.

Reference: Oracle Cloud

Developing Applications with Oracle Visual Builder

"Use Messaging Patterns" -> "Dialogs".

2. Oracle Redwood Component Reference: The official component reference provides the specific tag names for Redwood components. It lists oj-sp-message-dialog-general

oj-sp-message-dialog-destructive

and oj-sp-message-unsaved-changes as available messaging components that function as modal dialogs.

Reference: Oracle Help Center

Visual Builder Redwood Component Reference

"oj-sp-message-dialog-general"

"oj-sp-message-dialog-destructive"

"oj-sp-message-unsaved-changes" component specifications.

The Redwood Reference App is an official Oracle tool designed to demonstrate the core patterns of the Redwood Design System. According to the official Redwood documentation, the app explicitly implements several key patterns to guide developers. Among these are the Start Page, which serves as the initial entry point for users; the Dashboard Landing Page, which provides a high-level overview of critical information and metrics; and the Smart Filter and Search, a powerful, integrated component for finding and refining data within the application. These three are foundational patterns showcased in the reference implementation.

C. Vertical Foldout: This describes a specific UI component or behavior, not a primary, named page pattern demonstrated in the Redwood Reference App.

D. Welcome Page: The functionality of a welcome page is incorporated into the "Start Page" pattern in Redwood; it is not a distinct, separately named pattern.

F. Data Grid Page: While applications built with Redwood use data grids (tables), "Data Grid Page" is not a formal page pattern. Data is presented within other patterns like List Pages or Dashboards.

1. Oracle Redwood Design System Documentation

Patterns - Start Page: "The Start page is the first page a user sees after signing in to an application... The Redwood Reference App includes an example of a Start page." (This confirms the Start Page pattern is in the reference app).

2. Oracle Redwood Design System Documentation

Patterns - Dashboard Landing Page: "A Dashboard Landing page provides an overview of key information and metrics... The Redwood Reference App includes an example of a Dashboard Landing page." (This confirms the Dashboard Landing Page pattern is in the reference app).

3. Oracle Redwood Design System Documentation

Patterns - Smart Filter and Search: "The Smart Filter and Search pattern combines search and filtering into a single

powerful component... See the Redwood Reference App for an implementation of this pattern." (This confirms the Smart Filter and Search pattern is in the reference app).