Get Salesforce Plat-Con-201 Exam Practice Questions - Real and Updated

Answer : A, D

The two pieces of data that the consultant should recommend displaying using FlexCards are: Policies including type, issue date, amount and Customer name, title, phone, email. A FlexCard is a tool that can display data and actions in a card format. The consultant can use FlexCards to show important and summary information about the customer and their policies, such as name, title, phone, email, type, issue date, and amount.These pieces of data are suitable for FlexCards because they are concise and relevant for the agents

Answer : B, C

When designing OmniScripts, the best practices that should be followed to optimize performance and user experience are:

Use a single DataRaptor to save the information: Instead of using multiple DataRaptors to update the account information after each step, it is better to use a single DataRaptor at the end of the OmniScript to save all the information at once. This reduces the number of database operations and improves performance.

Combine the three steps into one step: Instead of having three separate steps to capture the required information, it is better to combine them into one step with a simple layout. This reduces the number of page transitions and improves user experience.

The suggestions that are not best practices are:

Create a reusable OmniScript for this process: This may not be necessary if the process is specific to creating new billing accounts and not used by other OmniScripts. Creating a reusable OmniScript may add complexity and maintenance overhead.

Configure the save for later property: This may not be useful if the process is short and simple and does not require the user to resume it later. Configuring the save for later property may add unnecessary storage and retrieval logic.

Answer : D

The Action element that redirects the user outside an LWC OmniScript is Navigate. Navigate allows the user to navigate to a URL or a Salesforce record or page. Response, Done, and Post to Object are not Action elements, but End elements that terminate an OmniScript.

Answer : D

The number of different data sources that can be configured using FlexCards in this scenario is 6. A FlexCard can have one data source per state, and a state can have multiple child FlexCards, each with its own data source.Therefore, the parent FlexCard can have one data source for its state, and each of the 5 child FlexCards can have a different data source, making a total of 6 data sources

Answer : C

The two actions that the consultant should recommend to the project team are replace existing APEX using DataRaptors and HTTPActions, and implement FlexCards and OmniScripts for the front-end. Replacing existing APEX using DataRaptors and HTTPActions would reduce implementation time, as these tools are declarative and do not require coding. Implementing FlexCards and OmniScripts for the front-end would ensure end-user processes are as simple as possible, as these tools provide guided interactions and contextual data. Creating new LWC templates for branding and styling would increase implementation time, as this would require coding and testing. Using existing APEX classes as data sources would not ensure optimal UX, as this would limit the flexibility and scalability of the solution.