Oracle 1z0-1114-23 Oracle Redwood Application 2023 Developer Associate Exam Practice Test

This question tests your knowledge of how to share your AppUI extension in Visual Builder Studio with another developer for testing purposes. The correct answer is C, because you can choose the Share option from the menu in your workspace editor to generate a URL that you can send to another developer who can access your extension in read-only mode. The other options are incorrect, because they are not the best ways to share your extension for testing purposes. Here is why:

• Option A is incorrect, because creating a shared workspace with another developer would allow them to edit your extension as well as view it, which might not be what you want.
• Option B is incorrect, because clicking the Publish button in your workspace would push your changes to Git and also start a merge request, which might not be what you want if you are not ready to merge your changes yet.
• Option D is incorrect, because pushing your changes to a shared branch before pushing it to Git would require you to create another branch and also ask the other developer to switch to that branch in their workspace, which might be more complicated than simply sharing your URL.

References: [Sharing Your Workspace], [Publishing Your Changes]

The two tools that allow UI/UX Designers to reuse Redwood’s shared libraries and templates for projects and products are Figma and Adobe XD. These are popular design tools that support importing and exporting UI components, layouts, and styles. Redwood provides a toolkit for Figma and a plugin for Adobe XD that enable designers to access and use Redwood’s shared libraries and templates in their projects.

References: : Redwood Toolkit for Figma : Redwood Plugin for Adobe XD

The best option to fulfill this request is to use VB Studio in Fusion Apps. This is a feature of Visual Builder Studio that allows you to create AppUI extensions for Fusion Apps pages. You can use the same development platform that Oracle Cloud Applications are built on, leveraging the Redwood design system, templates, patterns, and components. You can also access data from Fusion Apps using the service catalog and deploy your extensions directly to your Fusion Apps instance.

References: : AppUI Extensions in Visual Builder Studio : Getting Started with Visual Builder Studio for Fusion Apps Extensions

When you subscribe to Oracle Fusion Cloud Applications, you get one instance of Oracle Visual Builder Studio provisioned with your Oracle Fusion Cloud Applications Tenancy.This instance is mapped to your production Fusion Apps instance and allows you to create and deploy extensions for your Fusion Apps pages. You can also use this instance to access other instances of Fusion Apps in your tenancy by creating sandboxes for them .

References: : Getting Started with Visual Builder Studio for Fusion Apps Extensions : Working with Sandboxes in Visual Builder Studio

The Object Card layout is suitable for displaying information about a product and using it as an entry point from where users can access additional details. The Object Card layout consists of a header with an icon and a title, a body with one or more fields or actions, and a footer with optional actions or indicators. The Object Card layout summarizes the available information about a product in a visually compact manner and allows users to perform actions on it or navigate to more details. Therefore, option A is the correct answer. References: [Object Card Layout], [oj-sp-object-card]

This question tests your knowledge of the Redwood patterns that are used in the Redwood Reference App, which is a sample application that showcases the Redwood design system and the best practices for creating engaging user interfaces with Visual Builder Studio. The correct answer is A, B, and E, because these are the three patterns that are used in the Redwood Reference App. The other options are incorrect, because they are not patterns, but components or templates that can be used in different contexts. Here is a brief description of each pattern:

• Start Page: This pattern is used to provide an overview of the app’s functionality and allow users to start a task or a workflow. It consists of a header with a title and subtitle, a primary action button, and a grid of cards with icons and labels.
• Dashboard Landing Page: This pattern is used to display key performance indicators (KPIs) and a dashboard grid with information visualizations that highlight and explain business performance. It consists of a header with a title and subtitle, a primary action button, an in-flow back button, and a dashboard grid with charts, gauges, or tables.
• Smart Filter and Search: This pattern is used to enable users to filter and search data based on various criteria and see the results in a table or a list. It consists of a header with a title and subtitle, a smart filter bar with input fields and chips, an optional search bar with suggestions, and a data grid or list with pagination and sorting.

References: [Redwood Reference App], [Redwood Patterns]

This question tests your knowledge of the dialog message components that are available in Redwood, which are used to interrupt the user and force them to make a decision. The correct answer is A, C, and E, because these are the three dialog message components that are available in Redwood. The other options are incorrect, becausethey are not dialog message components, but banner message components or page templates that can be used in different contexts. Here is a brief description of each dialog message component:

• oj-sp-message-dialog-destructive: This component is used to display a dialog message that warns the user about an irreversible action that will delete or destroy data. It has a red header with an icon and a title, a body with a message and an optional description, and two buttons for canceling or confirming the action.
• oj-sp-message-dialog-general: This component is used to display a dialog message that informs the user about an action that requires their confirmation or input. It has a blue header with an icon and a title, a body with a message and an optional description or input field, and one or more buttons for canceling or completing the action.
• oj-sp-message-unsaved-changes: This component is used to display a dialog message that alerts the user about unsaved changes that will be lost if they navigate away from the current page. It has a yellow header with an icon and a title, a body with a message and an optional description, and two buttons for discarding or saving the changes.

References: [Redwood Dialog Messages], [oj-sp-message-dialog-destructive], [oj-sp-message-dialog-general], [oj-sp-message-unsaved-changes]

The Publish button in the Visual Builder Studio workspace editor allows you to push your changes to the Git repository and also start a merge request. A merge request is a way of proposing changes from one branch to another branch in Git. It helps you to review and collaborate on your code before merging it into the main branch .

References: : Working with Git in Visual Builder Studio : Merge Requests in Visual Builder Studio

If Dave deployed an AppUI extension to an instance by mistake, he can fix this by undeploying the extension in the Visual Builder Studio’s Environment tab. The Environment tab shows all theFA instances that are connected to Visual Builder Studio and allows you to deploy or undeploy extensions to them. To undeploy an extension, Dave can select the instance and click on the Undeploy button next to the extension name. This will remove the extension from the instance and restore the original UI of Fusion Cloud Apps. Therefore, option B is the correct answer. References: [Undeploying Extensions from Fusion Applications], [Managing Environments]