Salesforce User-Experience-Designer Test Dumps

A.   Reframe the product objectives from multiple, diverse perspectives.

Answer DescriptionExplanation: Consequence scanning is a practice that helps teams to consider the potential consequences of their product or service on people, communities, and the planet1. It is an agile tool that fits within an iterative development cycle and allows teams to identify and mitigate risks, as well as focus on positive outcomes2. One of the goals of consequence scanning is to reframe the product objectives from multiple, diverse perspectives. This means that the team can explore how different stakeholders, such as users, organisations, or society, might be affected by the product or service, both intentionally and unintentionally2. By doing so, the team can ensure that the product or service aligns with their values and culture, and that they are aware of the trade-offs and implications of their decisions2. Reframing the product objectives from multiple, diverse perspectives can also help the team to discover new opportunities, generate innovative solutions, and increase user satisfaction and trust3.

Encouraging team well-being through collaboration and identifying the best angle for positive launch press coverage are not the primary goals of consequence scanning, although they might be beneficial side effects. Consequence scanning is not a PR exercise, but a way to ensure responsible innovation and ethical design2. While consequence scanning can foster team collaboration and communication, it is not a team-building activity, but a way to share knowledge and expertise and raise concerns in a dedicated format2.

B.   Invite team members to observe usability sessions

Answer DescriptionExplanation: One of the best ways to increase the acceptance of the results of a usability testing session is to invite the development team members to observe the usability sessions. By observing the sessions, the developers can see how the users interact with the product, what difficulties they face, what feedback they provide, and how they react emotionally. This can help the developers to empathize with the users, understand their needs and expectations, and appreciate the value of usability testing. Observing the sessions can also help the developers to identify and prioritize the issues that need to be fixed, and to collaborate with the UX designer on finding the best solutions. References: [How to Get Stakeholders to Buy into User Research] (https://ux.stackexchange.com/questions/31222/what-is-the-difference-between-usabilitytesting- and-user-acceptance-testing), [How to Involve Developers in User Research] (https://bing.com/search?q=usability+testing+acceptance)

A.   troubleshooting customer issues and logging activities

Answer DescriptionExplanation: When designing the experience for a 'Case Solver' user persona, especially in the context of Cloud Kicks' Service Cloud instance, the activities to consider should revolve around the primary responsibilities and tasks of this role. For a Case Solver, these would include:

Troubleshooting customer issues: This involves identifying, analyzing, and solving problems reported by customers. The design should facilitate easy access to relevant information, tools for effective problem-solving, and a seamless workflow for diagnosing issues.

Logging activities: Keeping a detailed record of interactions, solutions provided, and any follow-up actions is crucial. The user interface should support efficient logging and tracking of activities to ensure accountability and facilitate continuous improvement in customer service.

While training other agents and editing knowledge articles (option B) and viewing the status of cases and analyzing campaign metrics (option C) are important in certain contexts, they do not directly align with the core activities of a Case Solver persona focused on direct customer support and problem resolution.

B.   Clarity, Efficiency, Consistency, Beauty

Answer DescriptionExplanation:

The Salesforce Lightning Design System (SLDS) reflects the patterns and components that underpin the Salesforce product. These patterns and components provide a unified language and consistent look and feel when designing apps and products within the Salesforce ecosystem. The Lightning Experience UI, which SLDS represents, was crafted using four core design principles. We encourage you to keep them in mind as you develop your applications. They are:

Clarity — Eliminate ambiguity. Enable people to see, understand, and act with confidence.
Efficiency — Streamline and optimize workflows. Intelligently anticipate needs to help people work better, smarter, and faster.
Consistency — Create familiarity and strengthen intuition by applying the same solution to the same problem.
Beauty — Demonstrate respect for people’s time and attention through thoughtful and elegant craftsmanship. References: Introduction to the Salesforce Lightning Design System.

B.   44 pixels wide x 44 pixels tall

Answer DescriptionExplanation: According to the Salesforce Lightning Design System, the minimum touch screen target size for interactive elements on mobile devices is 44 pixels wide x 44 pixels tall. This size ensures that users can easily tap the elements without accidentally hitting the wrong ones or missing them entirely. The touch target size also takes into account the average finger size and the device resolution. Smaller touch targets may cause frustration and errors for users, especially those with low vision, motor impairments, or large fingers.

B.   Navigation items are configure in the Salesforce Navigation Setup mode.


C.   Visualforce pages and Lightning pages can be included

Answer DescriptionExplanation: The Salesforce Navigation Setup mode allows the administrator to customize the navigation menu and navigation bar of the Salesforce mobile app using the Mobile Only app. The administrator can select the Lightning pages, Visualforce pages, Lightning components, and other productivity items that they want to appear in the navigation menu and navigation bar. The administrator can also reorder the navigation items and create tabs for them. To customize navigation items, in the Quick Find box, enter Navigation, and select Salesforce Navigation 1. Visualforce pages and Lightning pages can be included in the navigation menu and navigation bar of the Salesforce mobile app, as long as they have tabs created for them. To create a tab, from Setup, enter Tabs in the Quick Find box, and select Tabs 1.

C.   A Key fields to complete before next Path stage

Answer DescriptionExplanation: The Path feature that should be used to add onboarding value for the sales representatives is the Key fields component. The Key fields component allows the admin to specify up to five fields that are important or required for each stage of the Path. The sales reps can see and edit these fields directly from the Path, without scrolling through the record page. This helps to guide the reps on what information they need to gather or update at each stage, and ensures data quality and completeness. The Key fields component can also be used to enforce validation rules or required fields, by preventing the reps from moving to the next stage until they fill out the necessary fields.

A.   Be specific about the issues testers encountered

Answer DescriptionExplanation: A usability testing report is a document that summarizes the findings and insights from a usability test, which is a method of evaluating a product or service by observing how real users interact with it. A usability testing report should provide clear and actionable recommendations for improving the user experience and usability of the product or service1. One of the best practices for presenting the findings of a usability testing report is to be specific about the issues testers encountered. This means describing the problems in detail, explaining how they affected the user’s performance and satisfaction, and providing evidence from the data collected, such as quotes, screenshots, videos, or metrics. Being specific about the issues helps to illustrate the severity and impact of the problems, as well as to justify the need for improvement2.
The other two options, reporting only the new issues and omitting already known bugs, and including the names of participants in the report, are not good practices for presenting the findings of a usability testing report. Reporting only the new issues and omitting already known bugs can create a biased and incomplete picture of the usability test results, as it can overlook the recurring and persistent problems that may still affect the user experience and usability of the product or service. Including the names of participants in the report can violate the ethical and legal principles of user research, such as confidentiality, anonymity, and informed consent, which require protecting the privacy and identity of the users who participate in the research3.