The Dashboard Landing Page template is a predefined layout that consists of a header with a title and subtitle, a primary action button, an in-flow back button, and a dashboard grid with information visualizations. The title property is required for this template, as it provides a descriptive name for the dashboard. The subtitle property is optional, as it provides additional information or context for the dashboard. The primary action property is also optional, as it defines an action that can be performed on the dashboard, such as creating a new item or filtering the data. The in-flow back property is only applicable when the dashboard is part of a flow or a drill-down navigation, as it allows the user to go back to the previous page. Therefore, option A is the correct answer. Reference: [Dashboard Landing Page Template], [oj-sp-dashboard-landing-page]

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.

You would need a Visual Builder service instance to deploy your app to in three cases:

When the app needs to be accessed by users who do not have Fusion Apps access: If you want your app to be available to users who are not authorized to access Fusion Cloud Apps, you need to deploy it to a stand-alone VB instance that has its own user management and security policies.

When there is an application that is accessible from a vanity URL (Custom domain): If you want your app to have a custom domain name that is different from the default VB instance URL, you need to deploy it to a stand-alone VB instance that supports custom domain configuration.

When gaining access to Oracle Fusion Apps REST services: If you want your app to access the REST services provided by Fusion Cloud Apps, such as querying or updating data, you need to deploy it to a VB instance that is connected to the FA instance and has the appropriate security roles and permissions. Therefore, options A, C, and D are the correct answers. Reference: [Deploying Visual Builder Apps], [Accessing Fusion Applications REST Services]

A build pipeline in Visual Builder Studio can deploy an AppUI extension to multiple FA instances by using the Deploy to FA Instance step. This step allows you to specify the target FA instance, the extension type, and the extension name. You can also use the Deploy to VB Instance step to deploy an AppUI extension to a stand-alone VB instance. Therefore, option D is the correct answer. Reference: [Deploying AppUI Extensions], [Deploying Extensions to Fusion Applications]

The easiest way to create a Foldout layout in a page emulating the one in Oracle Fusion Cloud Apps is to use the horizontal Foldout page template pattern. This is a predefined pattern that provides a horizontal fold animation for pages with multiple panels of data. You can drag and drop this pattern from the Components palette in Visual Builder Studio and configure it according to your needs.