1Z0-1114-25 Practice Questions

Visual Builder Studio (VBS) is Oracle's designated environment for extending Fusion Cloud Applications using the Redwood user experience. It directly exposes three key types of resources to facilitate this:

1. Fusion Cloud Apps REST endpoints: VBS includes a service catalog that allows developers to browse and select from the rich set of REST APIs exposed by the connected Fusion instance. This is the primary mechanism for data interaction.

2. Redwood templates and patterns: To ensure consistency and accelerate development, VBS provides a library of pre-built page templates and patterns that conform to the Redwood design system's principles and layouts.

3. Redwood UI components: The VBS visual designer includes a component palette with Oracle JET (JavaScript Extension Toolkit) components that are styled to match the Redwood look and feel, enabling the creation of compliant user interfaces.

A. Fusion Cloud Apps database tables: VBS does not provide direct access to the underlying database tables. Interaction with Fusion data is managed exclusively through the published REST APIs for security, stability, and encapsulation.

B. Fusion Cloud Apps action chains developed by Oracle: Action chains are a client-side construct within a Visual Builder application that defines its behavior. They are not artifacts exposed by the Fusion Cloud Apps backend service itself.

1. Oracle Cloud Infrastructure Documentation (Visual Builder): "About Developing Fusion Applications with Oracle Visual Builder Studio" states

"When you develop an extension

you'll use business objects from the Fusion Applications instance that your VB Studio instance is associated with. These business objects are exposed through a service catalog..." and "...you'll use the same Redwood components and page templates that Oracle uses to develop its own apps." This confirms the use of REST endpoints (via the service catalog)

Redwood components

and templates.

Source: Oracle Help Center

Develop Fusion Applications with Oracle Visual Builder Studio

"About Developing Fusion Applications with Oracle Visual Builder Studio".

2. Oracle Cloud Infrastructure Documentation (Visual Builder): "Add a Service Connection" section details how to connect to services. It explicitly mentions

"The catalog shows all the services available in the Oracle Fusion Cloud Applications instance that your visual application is associated with." This directly supports the exposure of REST endpoints.

Source: Oracle Help Center

Developing Applications with Oracle Visual Builder

"Working with Service Connections"

"Add a Service Connection".

3. Oracle Cloud Infrastructure Documentation (Visual Builder): "About Redwood" section explains

"To help you build apps that are consistent with the Redwood user experience

Visual Builder provides a wealth of resources

including a Redwood template... and a rich set of UI components that implement the Redwood design system." This confirms the availability of both Redwood templates and UI components.

Source: Oracle Help Center

Developing Applications with Oracle Visual Builder

"Building Your User Interface"

"About Redwood".

The Data Grid page pattern in Oracle Visual Builder is built upon the data management page template. This template utilizes an Advanced Collection Container component which can include optional drawers. These drawers are designed as side panels to display detailed information or transactional forms related to the selected data in the grid. The officially supported positions for these drawers are at the "start" (typically the left side in LTR languages) and the "end" (typically the right side) of the container.

C. Top position: The Data Grid pattern's drawer component is designed as a vertical side panel, not a horizontal panel at the top of the container.

D. Bottom position: Similar to the top position, the bottom is not a supported placement for drawers within this specific page pattern and component structure.

1. Oracle Visual Builder Documentation: Develop Applications with Oracle Visual Builder

Version 24.04

Chapter: "Work with Page Patterns". In the section "Data Management Page Pattern"

the documentation states: "The template encapsulates the Advanced Collection Container component

a Data Grid component

and optional drawers (start and end) in case you need extended options to review information or include transactional subflows related to the Data Grid."

2. Oracle Visual Builder Documentation: Develop Applications with Oracle Visual Builder

Version 24.04

Chapter: "Work with Collection Components". The section on the "Advanced Collection Container" describes its layout capabilities

including slots for start and end drawers

which confirms these as the designated positions for this type of functionality.

The Oracle Redwood design process is a structured, user-centered methodology. It mandates that a thorough understanding of the user's problem, goals, and context must be the first step. Following this foundational research, a clear vision for the solution is articulated. The process then moves to leveraging existing Redwood patterns and templates, refining the detailed design, specifying it for development, and finally, monitoring real-world engagement to inform future iterations. This sequence ensures that the final product is both effective and grounded in user needs.

A. This option is incorrect because articulating a vision without first understanding the problem leads to solutions that are not user-centered.

B. This option uses non-standard terminology ("Understand the statement") and does not follow the official Redwood design process sequence.

C. This option incorrectly prioritizes articulating a vision and selecting templates before the crucial first step of understanding the user's problem.

1. Oracle Redwood Design System Documentation: The official "Design Process" guide outlines the six key steps in the exact order presented in the correct answer. The process starts with "1. Understand the problem" and is followed by "2. Articulate the vision."

Source: Oracle. "Redwood Design System - Get Started - Design Process". Accessed on the official Oracle Redwood Design System website. (Note: Direct linking is not feasible

but the path is redwood.oracle.com -> Get Started -> Design Process).

Visual Builder Studio (VBS) provides a complete lifecycle management toolset for AppUI extensions. When an extension is deployed, it can be managed from the Environments tab within the VBS project. This interface allows a developer to view all deployed extensions for a specific environment and provides an explicit "Undeploy" action to remove an extension from the Fusion Cloud Apps instance. This is the standard, self-service procedure for correcting a mistaken deployment.

A. Oracle's quarterly updates apply to the base Fusion Cloud application and do not automatically remove custom extensions. Extension lifecycle is managed by the customer.

C. Opening a service request is for support issues, not for standard development lifecycle tasks like undeploying an application. This action is self-service within VBS.

D. Deployed extensions are not permanent. The ability to undeploy an extension is a fundamental feature of the development and deployment process in Visual Builder Studio.

1. Oracle Official Documentation - Developing Applications with Oracle Visual Builder Studio:

Source: Developing Applications with Oracle Visual Builder Studio

Chapter: "Deploying Your Visual Builder Extension"

Section: "Undeploy an Extension".

Content: The documentation explicitly states

"You can undeploy an extension that you no longer need from the Deployments tab of the Environments page." It then provides the step-by-step procedure: "In the navigation menu

click Environments. Select the environment where the extension is deployed. Click the Deployments tab. In the list of deployed extensions

find the extension you want to undeploy

click its Actions menu

and select Undeploy." This directly supports option B and refutes options C and D.

When developing an AppUI extension for Oracle Fusion Cloud Applications using Visual Builder Studio (VBS), the correct and standard method for accessing data is to use the integrated service catalog. VBS is tightly coupled with the Fusion Apps environment, and it automatically populates the catalog with the available, supported REST APIs from that instance. This approach simplifies service discovery, handles authentication seamlessly, and ensures that the extension interacts with the application through a secure and upgrade-safe API layer, which is a fundamental principle of SaaS extensibility.

B. Defining a service by direct URL is a generic method for connecting to any REST API but bypasses the integrated, simplified, and recommended workflow provided by the service catalog for Fusion Apps.

C. Direct database connections (JDBC) to the Fusion Apps database are strictly prohibited for AppUI extensions. All interactions must occur through the published application APIs to maintain security, integrity, and stability.

1. Oracle Visual Builder Documentation

"Develop Fusion Applications with Visual Builder Studio": In the section "About Services in Your Visual Application

" it states: "When you develop an extension of a Fusion Applications cloud service

the services available in that cloud service are automatically added to the Services pane in the Navigator

under the Fusion Applications node." This confirms the primary role of the integrated service list

which functions as the catalog.

2. Oracle Visual Builder Documentation

"Develop Fusion Applications with Visual Builder Studio": The chapter "Work with Services

Processes

and Events

" specifically the section "Create a Service Connection from the Service Catalog

" details the procedure. It begins

"The service catalog for your Fusion Applications cloud service contains a list of all the REST services that you can add to your extension." This explicitly identifies the service catalog as the intended mechanism.

3. Oracle Cloud Infrastructure Documentation

"Extend Fusion Apps with Oracle Visual Builder Studio": In the "About Extending Oracle Fusion Cloud Applications with Visual Builder Studio" overview

the architecture described is based on extending the UI and business logic through REST APIs. It does not mention or permit direct database access

implicitly invalidating the JDBC connection approach for SaaS extensions.

The Redwood platform is Oracle's comprehensive approach to user experience, encompassing a design system and a development platform. Its core features include being an end-to-end development platform (B) that provides tools and components to build applications from design to deployment. A primary goal of Redwood is to deliver a consumer-grade user experience (F), making complex enterprise software as intuitive and easy to use as modern consumer applications. The platform is inherently designed to be scalable and robust, enabling developers to manage both simple and highly complex business capabilities (A) required by Oracle's extensive suite of cloud applications.

C. Developer-grade user experience: This is incorrect. Redwood's primary goal is to provide a "consumer-grade" user experience for the end-users of the application, not a "developer-grade" one.

D. Manage only simple capabilities: This is incorrect. Redwood is the foundation for Oracle's large-scale enterprise applications (e.g., Fusion Cloud ERP, HCM), which are inherently complex.

E. No differentiated user experience: This is incorrect. Redwood's purpose is to create a consistent, modern, and highly differentiated user experience that sets Oracle applications apart.

1. Oracle Corporation

"Redwood." Oracle.com. Accessed 2024. On its main page

Oracle describes Redwood as a "shared design system

platform

and components to build applications that are both powerful and easy to use

" which supports its ability to handle complexity (A) and function as an end-to-end platform (B).

2. Oracle Corporation

"The Redwood Experience: A New Standard for Enterprise Applications." Oracle Blogs

October 20

2022. This official blog post states

"The Redwood design system delivers a consumer-grade user experience that is simple

intuitive

and relevant." This directly supports option (F).

3. Oracle Corporation

"Oracle Redwood Design System." design.oracle.com. Accessed 2024. The official design system documentation details the components and patterns used across Oracle's product portfolio

demonstrating its application in complex enterprise scenarios (A) and its function as a complete system for developers (B).

The Redwood design methodology prescribes a structured, user-centric approach to application development. The process logically begins with gaining a comprehensive understanding of the core problem. Following this, specific user goals are articulated to define what the user needs to achieve. The next step is to model the data required to support these goals. This initial framework is then presented to product management and other stakeholders to gather feedback for validation. Finally, the process is iterative, refining the understanding and design based on the feedback received until clarity and consensus are achieved. This sequence ensures the application is built on a solid, validated foundation.

A. Gathering feedback before understanding the problem is illogical. You must first define the problem to solicit relevant feedback.

B. Describing the data shape is a detailed implementation step that should follow a clear understanding of the problem and user goals.

D. Writing user goals without first understanding the overarching problem can lead to misaligned or incomplete requirements.

1. Oracle Visual Builder Documentation. In the guide for developing applications

the process for starting with the Redwood reference app is outlined. The section "Understand the problem" explicitly lists the steps in the correct sequence: "1. Understand the problem. 2. Write user goals. 3. Describe the shape of the data for your use case. 4. Gather feedback from product management and other stakeholders. 5. Iterate until you achieve clarity."

Source: Oracle Help Center

Developing Applications with Oracle Visual Builder

"Get started with the Redwood reference app"

Section: "Understand the problem".

2. Redwood Design System Principles. The official Redwood documentation emphasizes a design-led

user-centric approach. This philosophy inherently supports a process that starts with understanding the problem and the user's context before moving to more concrete design and data modeling tasks.

Source: redwood.oracle.com

"About Redwood" and "Get Started" sections.

The Oracle Redwood design system is engineered to provide a consistent, high-quality user experience out-of-the-box. Its core components and patterns are built with three key functionalities in mind:

1. Responsiveness: Redwood layouts and components automatically adapt to various screen sizes and devices, from mobile phones to large desktops, ensuring a seamless experience.

2. Accessibility (a11y): Components are developed following WCAG standards, incorporating features like keyboard navigation and ARIA attributes to be usable by people with disabilities.

3. Localization (l10n): The framework is designed for global applications, with built-in support for translation bundles and right-to-left (RTL) languages, allowing developers to easily adapt applications for different regions.

B. Caching services: Caching is a data or infrastructure-level concern, not a core, out-of-the-box functionality of the Redwood UI design system itself.

E. Telemetry and feedback: While Oracle applications may include telemetry, this is an application monitoring or platform-level service, not a built-in feature of the Redwood component library.

1. Oracle Redwood Design System - Accessibility: "Redwood is committed to accessibility and we build our components to be accessible from the start. We follow the W3C's Web Content Accessibility Guidelines (WCAG) 2.1 Level AA." This directly supports option D.

Source: Oracle Redwood Official Documentation

"Resources > Accessibility".

2. Oracle Visual Builder Documentation - Responsiveness: "The components and patterns that you use to build your application's pages are responsive by design... You can use responsive helper classes to further refine your UI's layout on different screen sizes." This supports option C.

Source: Oracle Cloud Infrastructure Documentation

"Develop Applications with Oracle Visual Builder"

Chapter: "Create a Responsive UI".

3. Oracle Visual Builder Documentation - Localization: "Visual Builder is designed to support the internationalization and localization of applications... When you enable localization

your visual application is set up with a default resource bundle... that contains the translatable strings in your application." This supports option A.

Source: Oracle Cloud Infrastructure Documentation

"Develop Applications with Oracle Visual Builder"

Chapter: "Internationalize Your Application".

When you create a new AppUI Oracle Application Extension in Visual Builder Studio (VB Studio), the action scaffolds a new set of source files (metadata, HTML, JavaScript, etc.) within your project's workspace. This workspace is backed by a Git repository. The extension exists purely in this design-time environment and is not deployed to any live instance. Deployment to the Oracle Fusion Cloud Applications instance is a separate, explicit action that you initiate through a build and deployment pipeline after you have developed and tested your extension. Therefore, none of the provided deployment or overwrite options (A, B, C, D) occur upon the initial creation of the extension.

A. The extension is deployed on the Fusion Application instance: Deployment is a distinct, subsequent step performed via a CI/CD pipeline after the extension is created and developed, not during creation.

B. The extension is deployed on a stand-alone Visual Builder instance: The extension is developed within the integrated VB Studio environment; it is not deployed to a separate, stand-alone instance upon creation.

C. The extension is deployed to the Fusion Apps database: The extension's source files are stored in the project's Git repository upon creation, not deployed to the Fusion Applications database.

D. The extension overwrites an existing page in Fusion Applications: Extensions are designed to be layered safely on top of existing pages. Overwriting does not occur, and any changes are only applied after a successful deployment.

1. Oracle Visual Builder Studio Documentation

"Create an Application Extension": "When you create an application extension

VB Studio creates a workspace for you with a Git repository that contains the source files for your extension. You can then use the tools in the workspace to modify the source files." This section describes the creation of a workspace and Git repository

with no mention of automatic deployment.

2. Oracle Visual Builder Studio Documentation

"Deploy an Application Extension": "After you've developed and tested your application extension

you'll want to deploy it to your Oracle Cloud Application instance. To deploy your extension

you'll use a pipeline that contains a build job that packages and deploys the extension." This explicitly defines deployment as a separate process from creation and development.

Fusion Cloud environments already embed a Visual Builder runtime, but that runtime is constrained to the Fusion tenancy, Fusion-authenticated users, and OAuth-secured services.

You therefore need a separate OCI Visual Builder service instance when:

• the application must be reachable by users who are not provisioned in Fusion Apps (A);

• the app must call an external REST API or database that is protected only with Basic Authentication, which the embedded runtime does not support (B);

• the app has to be exposed through a vanity/custom domain, something not configurable in the embedded runtime (C).

Calling Fusion REST services (D) and adding the app to the Fusion Apps menu (E) are already supported directly by the embedded runtime, so a separate instance is unnecessary.

D. Embedded Visual Builder already contains pre-configured OAuth trust to call Fusion REST; no extra instance is needed.

E. Fusion’s App Composer lets you register a Visual Builder extension in the Cloud Apps menu without deploying it to an external instance.

1. Oracle Help Center – “Extending Oracle Fusion Cloud Applications with Oracle Visual Builder”

24D

Section “When Do I Need a Stand-alone Visual Builder Instance?” (lists external users

basic-auth services

custom domain use cases).

2. Oracle Help Center – “Creating Service Connections” › “Authentication Options” (notes Basic Auth not allowed in embedded Fusion Visual Builder); Visual Builder 24.2 documentation

chap. 6.

3. Oracle Help Center – “Publishing Your Application” › “Use a Custom Domain”

Visual Builder 24.2

pp. 215-218 (custom domain requires OCI VB instance).

4. Oracle Help Center – “Calling Fusion Cloud REST APIs from Visual Builder Extensions”

Extensibility Guide 24D

sec. 8.1 (shows direct access without extra instance).

5. Oracle University Courseware – “Oracle Cloud: Extending Fusion Applications with Visual Builder”

Module 4

slides 18-20 (menu integration done within embedded runtime).