QUESTION: 77

A group of sales users needs to be guided step by step through a new process using Floating or Decked Prompts.
Their administrative teamwants to the ability to see the adoption of this assistance via Reports and Dashboards.

in-App Guidance Prompts using myTrailhead
Custom build using Salesforce Flow
Basic In-App Guidance Prompts
Use the Walkthrough App from AppExchange

Answer(s): D

Explanation:

The best option for guiding sales users through a new process using floating or docked prompts is to use the Walkthrough App from AppExchange. This app allows admins to create and manage in-app guidance walkthroughs using clicks, not code. Walkthroughs are interactive tutorials that guide users through a series of steps on a Lightning page. Users can see the prompts, click the action buttons, and follow the instructions to complete the process. Admins can also track the engagement and completion of the walkthroughs using reports and dashboards. The Walkthrough App is compatible with the standard in-app guidance feature, and does not require a subscription to myTrailhead1 . The other options are not suitable for this scenario because:
In-App Guidance Prompts using myTrailhead: This option requires a subscription to myTrailhead, which is a customizable learning platform that allows admins to create their own content and branding. In-app guidance prompts are one of the features of myTrailhead, but they are not the same as walkthroughs. Prompts are single-step messages that appear on a Lightning page, while walkthroughs are multi-step tutorials that guide users through a process. Prompts can be used to provide tips, announcements, or links, but they cannot show users how to perform a task. Custom build using Salesforce Flow: This option requires coding and development skills, which may not be available or feasible for the admin team. Salesforce Flow is a tool that allows admins to automate processes and tasks using clicks or code. Flows can be triggered by various events, such as buttons, actions, schedules, or record changes. Flows can also display screens to users, which can contain fields, text, images, or components. However, screens are not the same as prompts or walkthroughs. Screens are part of a flow logic, and they require user input to proceed to the next step. Screens cannot be customized to appear as floating or docked prompts, and they cannot guide users through a Lightning page.
Basic In-App Guidance Prompts: This option does not require a subscription to myTrailhead, but it also does not provide the functionality of walkthroughs. Basic in-app guidance prompts are the same as the ones mentioned in the first option, but without the customization and branding of myTrailhead. Basic prompts can be created and managed using clicks, not code, and they can be filtered by profiles and permissions. However, basic prompts are still single-step messages that appear on a Lightning page, and they cannot show users how to perform a task.

Reference:

: [In-App Guidance Walkthroughs: Getting Started for Sales Users] : [In-App Guidance Dashboard: Walkthrough Engagement]
: [In-App Guidance in Lightning Experience]
: [Salesforce Flow | Salesforce Developer Center]
: [Salesforce Flow Workflow Automation Tools - Salesforce.com] : [The Complete Guide to Salesforce Flow | Salesforce Ben] : [Trailhead | The fun way to learn]
: [Editions & Pricing - myTrailhead- Salesforce]
: [Salesforce introduces myTrailhead, a personal learning platform ...] : [Trailhead | The fun way to learn Salesforce]
: [Getting Started with myTrailhead - Salesforce]

Reveal Solution Next Question

QUESTION: 78

Cloud Kicks (CK) is planning to roll out a refreshed version of its mobile app with some new functionality for customers.
What are two reasons why CK's UX Designer would consider using an interactive prototype in this situation?
Choose2 answers.

To increase the speed of design compared to paper prototyping
To eliminate the need for journey mapping during discovery
To avoid added long-term cost from oversight-driven rework
To enable iterative feedback from the users

Answer(s): C,D

Explanation:

An interactive prototype is a simulation of the final product that allows users to interact with it and test its functionality and usability. An interactive prototype can be created using tools such as Figma or Invision, and can be shared with stakeholders and users for feedback and validation. An interactive prototype can have several benefits for a UX designer, especially when planning to roll out a refreshed version of a mobile app with some new functionality for customers. Two of these benefits are12:
To avoid added long-term cost from oversight-driven rework. An interactive prototype can help the UX designer to identify and fix any errors, bugs, or gaps in the design before the development stage. This can save time and money that would otherwise be spent on reworking the product after it is developed. An interactive prototype can also help the UX designer to ensure that the new functionality is aligned with the customer needs and expectations, and that it does not compromise the existing functionality or performance of the app.
To enable iterative feedback from the users. An interactive prototype can provide a realistic and engaging user experience, and allow the users to explore the app and provide their opinions and suggestions. The UX designer can use the user feedback to iterate and improve the design, and to validate the assumptions and hypotheses. An interactive prototype can also help the UX designer to measure the user satisfaction and loyalty, and to test the app's usability and accessibility. The following two reasons are not valid for using an interactive prototype in this situation:
To increase the speed of design compared to paper prototyping. An interactive prototype is not necessarily faster than a paper prototype, as it requires more time and effort to create and refine. A paper prototype is a low-fidelity prototype that uses sketches or drawings to represent the app's layout and functionality. A paper prototype can be useful for generating and testing ideas quickly and cheaply, and for involving the users in the co-design process. To eliminate the need for journey mapping during discovery. An interactive prototype is not a substitute for journey mapping, but a complement. Journey mapping is a UX research method that visualizes the user's journey across the app, and identifies the touchpoints, actions, emotions, and pain points. Journey mapping can help the UX designer to understand the user's context, goals, and needs, and to discover the opportunities for improvement. An interactive prototype can help the UX designer to test and validate the journey map, and to communicate the design vision to the stakeholders and users.

Reference:

Interactive Prototypes Without Coding - Studio by UXPin, What is Interactive Prototypes? -- updated 2023 | IxDF, Paper Prototyping as a Usability Testing Technique, Journey Mapping 101 | Nielsen Norman Group

Reveal Solution Next Question

QUESTION: 79

Cloud Kicks (CK) has not migrated to Lightning Experience but wants to leverage the Salesforce Lightning Design System (SLDS) in its custom applications.
Which three solutions should CK's designers use to deliver applications with a consistent Lightning Experience Look and feel?

Choose 3 answers

Local Development Server
iOS Static Library
Lightning Stylesheets for Visualforce
Standard Design Tokens
Heroku

Answer(s): C,D,E

Explanation:

Cloud Kicks (CK) can use the following three solutions to leverage the Salesforce Lightning Design

System (SLDS) in its custom applications, without migrating to Lightning Experience:
Lightning Stylesheets for Visualforce: This solution allows CK to apply the SLDS styles to its existing Visualforce pages, without having to rewrite the markup or use a static resource. By adding the attribute lightningStylesheets="true" to the <apex:page> tag, CK can automatically transform the standard Visualforce components into their SLDS equivalents, and give the pages a consistent Lightning Experience look and feel.
Standard Design Tokens: This solution allows CK to use the SLDS design tokens, which are predefined variables that store the visual design attributes of the SLDS, such as colors, fonts, sizes, and spacing. By using the design tokens, CK can ensure that its custom applications follow the SLDS guidelines and remain consistent with the Lightning Experience theme. CK can access the design tokens through the Lightning Design System Scoping tool, or by downloading them as a static resource3 . Heroku: This solution allows CK to build and deploy its custom applications on Heroku, a cloud platform that supports various languages and frameworks, such as Node.js, Java, or PHP. By using Heroku, CK can leverage the SLDS resources, such as the base components, the tokens, and the design patterns, to create web applications that have a consistent Lightning Experience look and feel. CK can also use the Lightning Out feature to embed Lightning components into its Heroku applications, and use the Lightning Web Components framework to create reusable UI elements .

Reference:

[Lightning Stylesheets for Visualforce | Salesforce Trailhead]1 [Lightning Stylesheets for Visualforce | Salesforce Developers]2 [Design Tokens | Lightning Design System]3
[Using Design Tokens | Lightning Aura Components Developer Guide | Salesforce Developers] [Build Apps with Lightning Design System | Salesforce Trailhead] [Lightning Web Components | Salesforce Developers]

Reveal Solution Next Question

QUESTION: 80

A UX Designer presents a creativedesign approach to solving end-user problems, beginning with identifying their needs and ending with creating solutions that meet those needs.
Which approach is being followed?

Salesforce Declarative Design
Digital Declarative Design
Human-Centered Design
User Interface Design

Answer(s): C

Explanation:

The approach that is being followed by the UX Designer is the Human-Centered Design. This is a creative design approach that focuses on understanding the end-user's needs, problems, and context, and then creating solutions that are desirable, feasible, and viable for them. The Human- Centered Design process typically involves four phases: empathize, define, ideate, and prototype.

Reference:

: Human-Centered Design
: Empathize, Define, Ideate, Prototype

Reveal Solution Next Question

Free USER-EXPERIENCE-DESIGNER Exam Braindumps (page: 20)

QUESTION: 77

Explanation:

Reference:

QUESTION: 78

Explanation:

Reference:

QUESTION: 79

Explanation:

Reference:

QUESTION: 80

Explanation:

Reference: