QUESTION: 81

A UX Designer wants to plan and communicate the intended page layouts of a community portal.
Which tool should they use?

Journey Mapping
Wireframes
Personas
Process Flows

Answer(s): B

Explanation:

The tool that the UX Designer should use to plan and communicate the intended page layouts of a community portal is wireframes. Wireframes are low-fidelity sketches or diagrams that show the basic structure, content, and functionality of a web page or app screen. Wireframes help the UX Designer to visualize the layout of the portal, arrange the elements according to their importance and relevance, and communicate the design concept to the stakeholders and developers. Wireframes are one of the learning objectives for the Salesforce User Experience Designer certification 1.

Reference:

[Wireframes - Lightning Design System]

https://careerfoundry.com/en/blog/ux-design/website-app-wireframe-examples/

Reveal Solution Next Question

QUESTION: 82

A developer is creating a Lightning Web Component (LWC) and wants to make sure the visual experience is consistent with Cloud Kicks' branding. The developer asks their UX Designer about the Salesforce Lightning Design System (SLDS) stylinghooks.
How should the designer describe them?

They use standard CSS properties to directly style HTML elements.
They use standard CSS properties to easily style base and custom components.
They use custom CSS properties to directly style HTML elements.
They use custom CSS properties to easily style base and custom components.

Answer(s): D

Explanation:

Styling hooks are CSS custom properties that allow developers to customize the appearance of base and custom components in a consistent and supported way. They work with web components and shadow DOM, which provide encapsulation and modularity for LWC. Styling hooks use the -- slds namespace and follow a naming convention that reflects the component, category, property, attribute, and state of the element being styled. For example, --slds-c-button-brand-color- background-hover is a styling hook for the button component, brand category, color background property, and hover state. Styling hooks can be declared in the CSS file of the LWC or in a global CSS file that affects all components on the page. Styling hooks are not standard CSS properties, but custom ones that are defined by SLDS and applied to the components using the var() function.

Reference:

Styling Hooks - Lightning Design System
SLDS Styling Hooks | Lightning Web Components Developer Guide | Salesforce Developers dxp Styling Hooks | LWR Sites for Experience Cloud | Salesforce Developers

The Salesforce Lightning Design System (SLDS) styling hooks use standard CSS properties to easily style base and custom components. Salesforce documentation states that "SLDS styling hooks are CSS classes that give you access to the same styling used in the Salesforce Lightning Design System. They make it easy to style base and custom components with the same look and feel" [1].
[1] https://developer.salesforce.com/docs/component-
library/documentation/lwc/lwc.use_slds_styling_hooks

Reveal Solution Next Question

QUESTION: 83

A UX Designer is considering the design of arecord creation screen for the custom object Appointment.
Appointment records have to record types: Virtual and In-Person, Virtual appointments may have different virtual meeting software options, each with fields specific to it.
Which two considerations should be made when creating this record using Dynamic Forms? Choose 2 answers

The use of tabs when creating the record is not allowed.
The form will not be available on mobile devices.
All software option sections of the form will always bevisible.
Fields can be organized into sections.

Answer(s): A,D

Explanation:

Dynamic Forms is a feature that allows users to customize the form fields and sections displayed to users on a page layout. Dynamic Forms can be used to create user-centric, intuitive, and dynamic record creation screens for custom objects, such as Appointment.
When creating a record using Dynamic Forms, the UX designer should consider the following two aspects12:
The use of tabs when creating the record is not allowed. Dynamic Forms does not support the use of tabs within the form, as tabs are not compatible with the record creation process. Tabs are only available for viewing or editing existing records, not for creating new ones. Therefore, the UX

designer cannot use tabs to separate the fields for different record types or software options on the record creation screen.
Fields can be organized into sections. Dynamic Forms allows the UX designer to group fields into sections, and place them anywhere on the page layout. Sections can have labels, collapsible headers, and visibility rules. The UX designer can use sections to create a logical and clear structure for the form, and to show or hide fields based on user input, data, or profile. For example, the UX designer can create a section for each software option, and use visibility rules to display only the relevant section based on the user's selection.
The following two aspects are not true when creating a record using Dynamic Forms, and should be disregarded:
The form will not be available on mobile devices. Dynamic Forms is compatible with mobile devices, and the UX designer can preview and test the form on different device sizes and orientations. The form will automatically adjust to the screen size and layout of the mobile device, and provide a responsive and consistent user experience.
All software option sections of the form will always be visible. Dynamic Forms allows the UX designer to use visibility rules to control the visibility of fields and sections on the form. Visibility rules can be based on user input, data, or profile. The UX designer can use visibility rules to show or hide software option sections based on the user's selection of the record type or the software option. This can reduce the clutter and complexity of the form, and provide a personalized and flexible user experience.

Reference:

Get Started with Dynamic Forms Unit | Salesforce Trailhead, Salesforce Dynamic Forms: Overview & Deep Dive Tutorial, Dynamic Forms and Actions FAQ | Salesforce Help, Create Dynamic Forms with Visibility Rules | Salesforce Trailhead

Reveal Solution Next Question

QUESTION: 84

A UX Designer wants to use the Salesforce Lightning Design System (SLDS) to create consistent user interface across Cloud Kicks' various platforms.
On which three platforms could the designer use SLDS resources? Choose 3 answers

Android
Visualforce
Heroku
MuleSoft
Azure

Answer(s): B,C,E

Explanation:

The Salesforce Lightning Design System (SLDS) is a collection of design resources that help create consistent and beautiful user interfaces across various platforms. The SLDS includes base components, tokens, design patterns, icons, fonts, and more, that follow the design principles and best practices of Lightning Experience. The SLDS can be used on the following three platforms:
Visualforce: Visualforce is a framework that allows developers to create custom user interfaces for web and mobile applications on the Salesforce platform. Visualforce pages can leverage the SLDS styles to match the look and feel of Lightning Experience, without writing any CSS code. By adding the attribute lightningStylesheets="true" to the <apex:page> tag, Visualforce pages can automatically transform the standard Visualforce components into their SLDS equivalents.

Heroku: Heroku is a cloud platform that supports various languages and frameworks, such as Node.js, Java, or PHP. Heroku applications 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. Heroku applications can also use the Lightning Out feature to embed Lightning components into their pages, and use the Lightning Web Components framework to create reusable UI elements.
Azure: Azure is a cloud platform that offers various services and tools for building, deploying, and managing applications. Azure applications 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. Azure applications can also use the Lightning Out feature to embed Lightning components into their pages, 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 [Build Apps with Lightning Design System | Salesforce Trailhead]3 [Lightning Web Components | Salesforce Developers]4
[Salesforce Lightning Design System for Azure Web Apps | Microsoft Azure]5 [Lightning Web Components and Azure | Salesforce Developers]6

Reveal Solution Next Question

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

QUESTION: 81

Explanation:

Reference:

QUESTION: 82

Explanation:

Reference:

QUESTION: 83

Explanation:

Reference:

QUESTION: 84

Explanation:

Reference: