
必ず合格できるSalesforce User-Experience-Designer試験の正確な212問題と解答あります
最新 [2024年10月17日]2024年最新の実際にある検証済みのUser-Experience-Designer問題集
Salesforceユーザーエクスペリエンスデザイナー試験は、合計60問の多肢選択問題で構成されています。受験者は2時間以内に試験を完了し、合格するには68%のスコアを達成する必要があります。Salesforceは、対面コース、ウェビナー、学習ガイドなど、試験に備えて候補者が準備するための様々な学習資料やリソースを提供しています。また、Salesforceユーザーインターフェイスの設計に実践的な経験を積むことを推奨しており、試験合格の可能性を高めることができます。
Salesforce User-Experience-Designer(Salesforce Certified User Experience Designer)認定試験は、Salesforceが提供するプロフェッショナル認定であり、Salesforceプラットフォーム上のユーザーセントリックなインターフェースとエクスペリエンスの設計と開発に特化したいと願う個人向けに提供されます。この試験は、ユーザーエンゲージメントと満足度を向上させ、生産性を高め、ビジネス成果を推進するユーザーフレンドリーなインターフェースを設計および実装するために必要なスキルと知識を検証します。この認定は、顧客や組織のニーズに応える優れたユーザーエクスペリエンスを提供することに熱心なデザイナー、開発者、アーキテクトに最適です。
質問 # 35
Cloud Kicks's development team is working on the build of anew custom component using VS Code. They often have new CSS dasses and properties conflicting with the Salesforce Lightning Design System (SLDS).
What should simplify working with SLDS in Lightning Components?
- A. SLDS Validator extension for VS Code
- B. Salesforce Developer Console should beused instead
- C. Install SLDS creator from AppExchange
- D. Keep the SLDS Stylesheet open for reference
正解:A
解説:
Explanation
The SLDS Validator extension for VS Code is a tool that simplifies working with the Salesforce Lightning Design System (SLDS) in Aura and Lightning components. It provides code completion, syntax highlighting, and validation with recommended tokens and utility classes. It also scans the markup and validates it against a database of guidelines, tips, and best practices extracted from the SLDS documentation. It offers suggestions on how to improve the code and avoid conflicts with SLDS12. References: SLDS Validator - Visual Studio Marketplace, SLDS Validator for VS Code - Lightning Design System
質問 # 36
Cloud Kicks (CK) has finished conducting research and has synthesized the findings. CK nowplans to collaboratively redesign services with stakeholders to address issues uncovered in the study.
Which process should be used?
- A. Pitch Session
- B. Management Committee Meeting
- C. Service Usability Testing
- D. Service-Blueprinting Workshop
正解:D
解説:
A service-blueprinting workshop is a process that involves mapping out the flow of a service, identifying the touchpoints, actors, processes, and systems that are involved, and highlighting the pain points and opportunities for improvement. A service-blueprinting workshop is a collaborative and creative way to redesign services with stakeholders, as it allows them to see the big picture, empathize with the users, and co-create solutions. A service-blueprinting workshop is suitable for Cloud Kicks (CK) after they have finished conducting research and synthesizing the findings, as it will help them address the issues uncovered in the study and design better service experiences for their customers. References: Service Design Service Blueprints, How to create a service blueprinting facilitation guide, Workshop exercise: Service Blueprint
質問 # 37
A UX Designer has recently released a feature on experience Cloud and wants to know if the feature was successful and track usability over time.
Which research methodology should be used?
- A. Quantitative
- B. Qualitative
- C. Qualification
- D. Quantizing
正解:A
解説:
Explanation
Quantitative research methodology should be used to measure the success and usability of a feature on Experience Cloud. Quantitative research involves collecting and analyzing numerical data that can be measured, compared, or statistically tested. Quantitative research can help answer questions such as:
How many users are using the feature?
How often are they using it?
How long does it take them to complete a task with the feature?
How satisfied are they with the feature?
How does the feature affect key performance indicators, such as conversion rates, retention rates, or revenue?
Quantitative research methods can include surveys, analytics, A/B testing, usability testing, and benchmarking.
These methods can provide objective and reliable data that can be used to evaluate the impact and effectiveness of a feature on Experience Cloud.
Qualitative research methodology, on the other hand, involves collecting and analyzing non-numerical data that can reveal users' attitudes, behaviors, motivations, and preferences. Qualitative research can help answer questions such as:
Why are users using or not using the feature?
What are their pain points, needs, and goals with the feature?
How do they feel about the feature?
What are their expectations and feedback for the feature?
How does the feature fit into their context and workflow?
Qualitative research methods can include interviews, focus groups, observations, diary studies, and card sorting. These methods can provide rich and detailed insights that can be used to understand the user experience and identify opportunities for improvement.
Both quantitative and qualitative research methods are valuable for UX design, but they serve different purposes and answer different types of questions. In this case, the UX designer wants to know if the feature was successful and track usability over time, which are questions that can be best answered by quantitative research methods.
References: User Research Methods, Quantitative vs. Qualitative Usability Testing, 8 Essential Usability Testing Methods for UX Insights
質問 # 38
Cloud Kicks needs functional components that will be used on many pages. The components need to be consistent with the look and feel of Lightning Experience.
What does the Salesforce Lightning Design System (SLDS) provide that will ensure consistency?
- A. Component Blueprints
- B. JavaScript Frameworks
- C. Custom Lightning components
- D. Experience Lightning Components
正解:D
質問 # 39
A UX Designer is customizing the look and feel of a site using Experience Builder and needs to choose a color for the text and the background of the buttons.
Which accessibility guideline should be considered?
- A. Adaptable
- B. Distinguishable
- C. Navigable
正解:B
解説:
The accessibility guideline of distinguishable means that the information and user interface components must be presented to users in ways that are perceptible. This includes using sufficient contrast between text and background colors, providing text alternatives for non-text content, and making it easier for users to see and hear content. When choosing a color for the text and the background of the buttons, the UX Designer should consider the contrast ratio between them, which should be at least 4.5:1 for normal text and 3:1 for large text.
This will ensure that the buttons are visible and readable for users with different visual abilities. References:
* [1]: Web Content Accessibility Guidelines (WCAG) 2.1, Principle 1: Perceivable
* [2]: Web Content Accessibility Guidelines (WCAG) 2.1, Success Criterion 1.4.3 Contrast (Minimum)
質問 # 40
A UXDesigner is asked to design a new application built on Salesforce.
What should be their first step?
- A. Become familiar with theSalesforce Lightning Design System (SLDS) component blueprints.
- B. Find and review relevant AppExchange packages.
- C. Design a series of custom web component for the app.
- D. Create branding sets for each audience using Experience Builder.
正解:A
解説:
The Salesforce Lightning Design System (SLDS) is a collection of design guidelines, resources, and tools that help create consistent, beautiful, and accessible user experiences across the Salesforce platform1. Component blueprints are one of the key resources that the SLDS provides. They are framework-agnostic, accessible HTML and CSS code snippets thatcan be used to create UI elements such as buttons, cards, menus, and more2. A UX Designer who is asked to design a new application built on Salesforce should become familiar with the SLDS component blueprints as their first step, because they can help them to3:
* Understand the structure, behavior, and appearance of the standard Salesforce components and how they can be customized or extended.
* Follow the SLDS design principles and best practices, such as clarity, efficiency, consistency, and beauty.
* Ensure that the application is responsive, adaptive, and compatible with different devices and screen sizes.
* Leverage the SLDS design tokens, icons, and utilities to create a coherent and scalable visual language.
* Reduce the development time and effort by reusing the existing code and avoiding duplication.
The other options are not the best first steps for a UX Designer who is asked to design a new application built on Salesforce. Creating branding sets for each audience using Experience Builder is a later step that involves applying the visual identity and style of the application todifferent user segments and channels4. Finding and reviewing relevant AppExchange packages is a research step that can help to identify existing solutions or features that can be integrated or adapted to the application5. Designing a series of custom web components for the app is a development step that can be done after defining the requirements, wireframes, and prototypes of the application.
References:
* Lightning Design System, Lightning Design System Create the World's Best Enterprise App Experiences Design System Fundamentals Component Blueprints Ready-to-use HTML and CSS UI elements provide the foundation for Salesforce experience development Go to Blueprints Tokens Visual design values and attributes that ensure branding and UI consistency at scale View Tokens Design Guidelines Design principles and best practices that guide beautiful, consistent, user-friendly product experiences Read Guidelines Tools New! Easy-to-use tools help all Trailblazers optimize workflows and bring Salesforce ideas to life Get Tools
* Blueprint Overview - Lightning Design System, Blueprint Overview - Lightning Design System What's New Getting Started Platforms Design Guidelines Kinetics Accessibility Component Blueprints Overview Accordion Activity Timeline Alert App Launcher Avatar Avatar Group Badges Brand Band Breadcrumbs Builder Header Button Icons Cards Chat Docked Utility Bar Dueling Picklist Dynamic Icons Dynamic Menu Expandable Section Feeds File Selector Files Form Element Global Header Global Navigation Icons Illustration Input List Builder Lookups Map Menus Notifications Page Headers Panels Path Picklist Pills Progress Indicator Prompt Radio Button Group Rich Text Editor Scoped Notifications Scoped Tabs Select Spinners Tabs Textarea Tiles Timepicker Toast Tooltips Tree Grid Trees Trial Bar Vertical Navigation Vertical Tabs Visual Picker Welcome Mat Utilities Design Tokens Icons Tools Resources Blueprint Overview Component blueprints are framework agnostic, accessible HTML and CSS used to create components in conjunction with our implementation guidelines. For more details, check out the glossary on the FAQ page. Show Filters Showing 85 blueprints, 183 variants. Accordion Lightning Component Responsive Adaptive Styling Hooks Prototype Base Checkmark \nCheckmark \nActivity Timeline Responsive Adaptive Styling Hooks Prototype Base \n \n Alert Responsive Adaptive Styling Hooks Prototype Base Checkmark \nCheckmark \nApp Launcher Responsive Adaptive Styling Hooks Prototype Base Checkmark \n \nAvatar Lightning Component Responsive Adaptive Styling Hooks Prototype Base Checkmark \nCheckmark \nInitials Checkmark
\nCheckmark \nAvatar Group Responsive Adaptive Styling Hooks Prototype Base Checkmark \n
\nGrouped Checkmark \n \nBadges Lightning Component Responsive Adaptive Styling Hooks Prototype Base Checkmark \nCheckmark \nBrand Band Responsive Adaptive Styling Hooks Prototype Base Checkmark \n \nBreadcrumbs Lightning Component Responsive Adaptive Styling Hooks Prototype Base \n Checkmark \nBuilder Header Responsive Adaptive Styling Hooks Prototype Base \n
\n Toolbar \n \n Button Groups Lightning Component Responsive Adaptive Styling Hooks Prototype Base Checkmark \n \nList Checkmark \n \nRow Checkmark \n \nButton Icons Lightning Component Responsive Adaptive Styling Hooks Prototype Base Checkmark \n \nBordered Filled Container Checkmark \n \nBordered Inverse Checkmark \n \nBordered Transparent Container Checkmark \n
\nBrand Checkmark \n \nInverse Checkmark \n \nStateful Checkmark \n \nTransparent Container Checkmark \n \nButtons Lightning Component Responsive Adaptive Styling Hooks Prototype Base Checkmark \nCheckmark \nDual Stateful Checkmark \nCheckmark \nStateful Checkmark \nCheckmark
\nWith Icon Checkmark \nCheckmark \nCards Lightning Component Responsive Adaptive Styling Hooks Prototype Base Checkmark \nCheckmark \nEinstein Checkmark \nCheckmark \nWrapper Checkmark \nCheckmark \nCarousel Lightning Component Responsive Adaptive Styling Hooks Prototype Base Checkmark \n \nChat Responsive Adaptive Styling Hooks Prototype Base Checkmark \n
\nPast Checkmark \n \nCheckbox Lightning Component Responsive Adaptive Styling Hooks Prototype Base Checkmark \nCheckmark \nForm Element Checkmark \nCheckmark \nCheckbox Button Lightning Component Responsive Adaptive Styling Hooks Prototype Base Checkmark \n \nCheckbox Button Group Responsive Adaptive Styling Hooks Prototype Base Checkmark \n \nCheckbox Toggle
* UX Designer Certification Prep: Design System Fundamentals, UX Designer Certification Prep: Design System Fundamentals Learn how to use the Salesforce Lightning Design System (SLDS) to create consistent, beautiful, and accessible user experiences across the Salesforce platform. Add to Favorites Add to Trailmix tags ~1 hr 30 mins +500 points Module Design System Fundamentals Learn about the Salesforce Lightning Design System (SLDS) and how it can help you create consistent, beautiful, and accessible user experiences across the Salesforce platform. 4 hrs 15 mins +800 points Project Build a Bear-Tracking App with Lightning Web Components Use Lightning Web Components and the Salesforce Lightning Design System to build a bear-tracking app. 2 hrs 15 mins +500 points Project Build a Conference Management App with Aura Components Use Aura Components and the Salesforce Lightning Design System to build a conference management app. 2 hrs 15 mins +500 points Project Build a Discount Calculator with Visualforce Use Visualforce and the Salesforce Lightning Design System to build a discount calculator. 2 hrs 15 mins +500 points Project Build a Survey App with Experience Builder Use Experience Builder and the Salesforce Lightning Design System to build a
* survey app. 2 hrs 15 mins +500 points Project Build a Travel Approval App with Lightning Flow Use Lightning Flow and the Salesforce Lightning Design System to build a travel approval app. 2 hrs 15 mins +500 points Project Build a Volunteer Management Appwith Lightning App Builder Use Lightning App Builder and the Salesforce Lightning Design System to build a volunteer management app. 2 hrs 15 mins +500 points Project Build an Expense Tracker App with Lightning Web Components Use Lightning Web Components and the Salesforce Lightning Design System to build an expense tracker app. 2 hrs 15 mins +500 points Project Build an Inventory Management App with Aura Components Use Aura Components and the Salesforce Lightning Design System to build an inventory management app. 2 hrs 15 mins +500 points Project Build an Order Management App with Visualforce Use Visualforce and the Salesforce Lightning Design System to build an order management app. 2 hrs
15 mins +500 points Project Build an RSVP Management App with Experience Builder Use Experience Builder and the Salesforce Lightning Design System to build an RSVP management app. 2 hrs 15 mins
+500 points Project Build an SMS Notification App with Lightning Flow Use Lightning Flow and the Salesforce Lightning Design System to build an SMS notification app. 2 hrs 15 mins +500 points Project Build an
* Branding Sets Unit | Salesforce Trailhead, Branding Sets Unit | Salesforce Trailhead Branding Sets Learn how to use branding sets to apply different styles to your digital experiences. Add to Favorites Add to Trailmix tags ~20 mins Incomplete Branding Sets Customize the look and feel of your digital experiences with branding sets. 15 mins +200 points Quiz +200 points Get Started with Branding Sets Learn how to create and apply branding sets to your digital experiences. 5 mins +200 points Quiz +200 points
* AppExchange Basics Unit | Salesforce Trailhead, AppExchange Basics Unit | Salesforce Trailhead AppExchange Basics Learn how to find, try, buy, and install AppExchange solutions. Add to Favorites Add to Trailmix tags ~25 mins Incomplete AppExchange Basics Learn how to find, try, buy, and install AppExchange solutions. 20 mins +200 points Quiz +200 points Get Started with AppExchange Learn what AppExchange is and how it can help you extend Salesforce functionality. 5 mins +200 points Quiz
+200 points
質問 # 41
A UX Designer at Cloud Kicks wants to utilize a design thinking approach for the design of new customer services.
Which approach combination encourages more creative problem-solving?
- A. Simple and innovative
- B. Agile and efficient
- C. Divergent and convergent
正解:C
解説:
Explanation
A design thinking approach is a human-centered method for solving complex problems and creating innovative solutions. It involves understanding the needs and desires of the users, generating and testing multiple ideas, and iterating on the feedback and results. A design thinking approach can be divided into two types of thinking: divergent and convergent. Divergent thinking is the process of generating many possible solutions to a problem without judging or filtering them. It encourages creativity, exploration, and experimentation. Convergent thinking is the process of evaluating, selecting, and refining the best solution to a problem. It involves analysis, logic, and criteria. Divergent and convergent thinking are complementary and cyclical. They help the designer to expand the solution space and then narrow it down to the most feasible and desirable option. By using both types of thinking, the designer can encourage more creative problem-solving and avoid premature convergence or fixation on a single idea. Therefore, the best approach combination for the UX Designer at Cloud Kicks is divergent and convergent thinking. References: Trailhead: Design Thinking, Trailhead: Salesforce User Experience Designer Certification Prep, Divergent and Convergent Design Thinking
質問 # 42
Sales managers want their team members to help each other close Opportunities. The Opportunity and Account organization-wide defaults are private. To grant Opportunity access to sales reps on the same team, owner ship-based sharing rules were created for each team.
What is the side effect of this approach?
- A. Sales Reps on the same team will have Edit access to the Accounts for Opportunities owned by then team members.
- B. All sales reps will have Read access to Accounts for all Opportunities.
- C. All sales reps will have Read access to all Accounts.
- D. Sales reps on the same team will have Read access to the Accounts for Opportunities owned by their team members.
正解:D
質問 # 43
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
- A. Azure
- B. MuleSoft
- C. Heroku
- D. Android
- E. Visualforce
正解:A、C、E
解説:
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 equivalents12.
* 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 elements34.
* 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 elements56.
References:
* [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
質問 # 44
Cloud Kicks' Sales team needs In-App Guidance for key functions and processes so they can maximize their time.
In which way should a UX Designer customize the Salesforce Help Menu to meet this request?
- A. Show a site map of all the content.
- B. Create a docked prompt based on new feature rollouts.
- C. Provide links to external resources, such as training videos or a company dictionary.
正解:A
解説:
Explanation
Confirmation bias is the tendency to seek, interpret, and remember information that confirms one's preexisting beliefs or hypotheses, while ignoring or discounting information that contradicts them1. Confirmation bias can affect user feedback sessions by influencing how the researcher designs the test, asks the questions, observes the behavior, and analyzes the data of the users. Confirmation bias can lead to inaccurate or incomplete insights, and ultimately to poor design decisions2.
One way to avoid confirmation bias in user feedback sessions is to allow the user to explore the application without specific questions regarding which tasks to perform. This can help the researcher to observe the user's natural and spontaneous interaction with the application, without imposing any expectations or assumptions on them. This can also help the user to express their honest opinions and feelings about the application, without being influenced by the researcher's questions or suggestions. This can result in more authentic and unbiased feedback, and more reliable and valid insights3.
Asking open-ended questions staying away from questions regarding feelings is not a good way to avoid confirmation bias in user feedback sessions, because it can limit the depth and richness of the feedback, and miss the opportunity to understand the user's emotions and motivations. Open-ended questions are questions that allow the user to answer in their own words, rather than choosing from a predefined set of options.
Open-ended questions are useful for eliciting more detailed and nuanced feedback, and for exploring the user's thoughts and feelings about the application. However, asking open-ended questions alone is not enough to prevent confirmation bias, as the researcher may still unconsciously frame the questions in a way that leads the user to confirm their hypotheses, or interpret the answers in a way that supports their beliefs. Asking questions regarding feelings is also important, as it can help the researcher to understand the user's emotional response to the application, and how it affects their satisfaction, engagement, and loyalty4.
Asking specific questions about known pain points to confirm your hypothesis is a bad way to avoid confirmation bias in user feedback sessions, because it can introduce the researcher's bias into the feedback process, and influence the user's perception and behavior. Asking specific questions about known pain points can lead the researcher to focus only on the information that confirms their hypothesis, and ignore or dismiss the information that challenges or contradicts it. It can also lead the user to pay more attention to the pain points that the researcher mentions, and overlook or downplay the other aspects of the application. This can result in skewed and distorted feedback, and misleading and invalid insights5.
References: 1: Confirmation bias - Wikipedia 2: How Confirmation Bias can affect user research | by Caroline Galipeau | UX Collective 3: 11 Types of Cognitive Biases to Avoid in User Research | Maze 4: How to Ask Good Questions in User Research | by Nick Babich | UX Planet 5: How to Avoid Confirmation Bias in User Research | by Sarah Doody | Medium
質問 # 45
How would a UX Designer Differentiate between voice and tone?
- A. Voice reflects the personality and tone is the way one speaks.
- B. Voice reflects the frequency and tone is one's pitch.
- C. Voice reflects the character and tone is one's strength.
- D. Voice reflects the expression and tone is the way one designs.
正解:A
解説:
Explanation
Voice and tone are two important aspects of UX writing that affect how users perceive and interact with a product. According to the Salesforce User Experience Designer Exam Guide, voice and tone are defined as follows:
Voice reflects the personality of the brand or product. It is consistent and does not change depending on the context or situation. Voice conveys the values, mission, and identity of the brand or product through the choice of words, phrases, and style of communication.
Tone reflects the way the voice speaks to the users. It is context-specific and can change depending on the user's mood, goal, and situation. Tone conveys the attitude, emotion, and empathy of the voice through the use of punctuation, grammar, and formatting.
For example, Mailchimp is a brand that has a distinctive voice and tone. Their voice is friendly, humorous, and quirky. Their tone varies depending on the user's experience, such as congratulating them for a successful campaign, or apologizing for an error. They use a tone map to guide their writers on how to adjust their tone for different scenarios.
References:
1: [Salesforce User Experience Designer Exam Guide]
2: [Voice and Tone | Salesforce Style Guide for Documentation and UX Writing]
3: [Voice and Tone | Salesforce Trailhead]
4: [UX writing 101: A beginner's guide to mastering tone of voice]
5: [Tone of Voice and User Experience | UX Magazine]
6: [Things I learned designing the voice and tone for our company]
7: [How to use voice and tone in UX writing]
8: [Voice and Tone | Mailchimp Content Style Guide]
質問 # 46
How would a UX Designer differentiate between voice and tone?
- A. Voice reflects frequency and tone is one's pitch.
- B. Voice reflects personality, and tone Is the way in which one speaks.
- C. Voice is how one speaks, and tone reflects personality.
正解:B
解説:
Voice and tone are two aspects of writing that affect how the reader perceives and responds to the content.
Voice is the consistent expression of the writer's or the brand's personality, values, and attitude. Voice reflects who the writer or the brand is, and what they stand for. Tone is the variation of the voice depending on the context, audience, and purpose of the content. Tone is the way in which the writer or the brand speaks to the reader, and how they convey their emotions, intentions, and expectations. Tone can change depending on the situation, the message, and the reader's needs and feelings12.
For example, at Salesforce, we have a voice that is friendly, helpful, and empowering. We use simple, clear, and conversational language that shows our respect and appreciation for our customers, partners, and community. We also use humor, metaphors, and storytelling to make our content engaging and memorable.
However, our tone can vary depending on thetype and goal of the content. For instance, when we write instructional content, such as Trailhead modules or user guides, our tone is more informative, instructive, and supportive. We use active voice, imperative mood, and positive feedback to guide the learner and encourage their progress. When we write promotional content, such as blog posts or social media posts, our tone is more persuasive, enthusiastic, and inspiring. We use rhetorical devices, emotional appeals, and calls to action to attract the reader and motivate them to take action34.
Therefore, a UX Designer would differentiate between voice and tone by understanding that voice reflects personality, and tone is the way in which one speaks. References: Voice and Tone - Lightning Design System, How To Create a Voice and Tone Program For Your Brand | Salesforce, Learn Why We Write the Way We Do Unit | Salesforce Trailhead, Write for Trailhead Unit | Salesforce Trailhead
質問 # 47
A UX Designer has created a new form for a call center that takes special delivery information from its customers.
The designer wants to ensure the call center staff finds the form easy and intuitive to use.
Which kind of testing should be conducted to validate this?
- A. Qualitative
- B. Focus Groups
- C. Usability Testing
- D. Survery
正解:A
質問 # 48
What are Salesforce core design principles when making design decisions?
- A. Emphasis, Efficiency, Repetition, Proportion
- B. Clarity, Efficiency, Balance, Proportion
- C. Clarity, Efficiency, Consistency, Beauty
- D. Emphasis, Alignment. Consistency, Beauty
正解:C
質問 # 49
A UX Designer wants to explore sample code for Lightning components and see how changing to code affects the visual appearance in real time, without deploying any code to a Salesforce org.
Whichtwo resources should help accomplish this?
Choose 2 answers
- A. Lightning Web Component Recipes App
- B. Develop Center's Lightning Component Library
- C. Local Development Server
- D. Lightning Design System Website
正解:C、D
解説:
Two resources that can help a UX Designer to explore sample code for Lightning components and see how changing the code affects the visual appearance in real time, without deploying any code to a Salesforce org, are:
* Lightning Design System Website. The Lightning Design System website is a resource that provides design guidelines, UI components, and code samples for building Lightning applications. The website also features a live code editor that allows the designer to edit and preview the code for Lightning web components and Aura components, and see the changes reflected in the browser instantly. The live code editor also provides syntax highlighting, auto-completion, and error checking features. The designer can use the Lightning Design System website to experiment with different code snippets and learn how to apply the design principles and best practices for Lightning components. Lightning Design System Website, [UX Designer Certification Prep: Salesforce Design System]
* Local Development Server. The Local Development Server is a resource that allows the designer to build, run, and test Lightning web components without deploying them to a Salesforce org. The Local Development Server is a CLI plug-in that creates a local web server that serves the Lightning web components from the local file system. The designer can use the Local Development Server to edit the code for Lightning web components in their preferred code editor, such as Visual Studio Code, and see the changes updated in the browser automatically. The Local Development Server also supports hot reloading, which preserves the component state and the browser session during code changes. The designer can use the Local Development Server to speed up the development and testing process and to debug thecode for Lightning web components. Local Development Server, [UX Designer Certification Prep: User Testing and Evaluation] The Lightning Web Component Recipes App and the Developer Center's Lightning Component Library are not resources that can help a UX Designer to explore sample code for Lightning components and see how changing the code affects the visual appearance in real time, without deploying any code to a Salesforce org.
The Lightning Web Component Recipes App is a sample application that showcases the functionality and best practices for Lightning web components. The Developer Center's Lightning Component Library is a reference guide that provides documentation and examples for Lightning web components and Aura components.
However, neither of these resources allow the designer to edit and preview the code in real time, as they require the code to be deployed to a Salesforce org or a scratch org first. Lightning Web Component Recipes App, Developer Center's Lightning Component Library, [UX Designer Certification Prep: User Testing and Evaluation] References: Lightning Design System Website, Local Development Server, Lightning Web Component Recipes App, Developer Center'sLightning Component Library, [UX Designer Certification Prep:
Salesforce Design System], [UX Designer Certification Prep: User Testing and Evaluation]
質問 # 50
Cloud Kicks (CK) has an Unlimited Edition Salesforce org. CK's UX Designer has identified that dynamic dashboards could be a useful tool to improve org usability and experience.
How many different dynamic dashboards could they create?
- A. Unlimited
- B. Up to 20
- C. Up to 10
- D. Up to 3
正解:A
質問 # 51
......
無料でゲット!2024年最新のに更新されたSalesforce User-Experience-Designer試験問題と解答:https://www.passtest.jp/Salesforce/User-Experience-Designer-shiken.html
合格させるUser-Experience-Designer試験には更新された212問題あります:https://drive.google.com/open?id=1RjiVk7qM297nEWGsH-702sDR2uV4WML9