[2024年12月08日]User-Experience-Designer試験問題集で100%合格率User-Experience-Designer試験！ [Q86-Q102]

A moderated usability study is a type of user research where the UX Designer interacts with the participants as they perform tasks on the prototype solution. The designer can ask follow-up questions to obtain further information about the issues participants may encounter, such as why they made certain choices, how they felt about the experience, and what they would like to see improved. This can help the designer gain deeper insights into the user needs, preferences, and pain points, as well as validate or invalidate their design assumptions. A moderated study also allows the designer to clarify any confusion or ambiguity that the participants may have during the session, and to adjust the tasks or scenarios as needed. References:
* [User Experience Designer Certification Prep: Conduct User Research]
* [User Experience Designer Certification Prep: Analyze User Research]
* [User Experience Designer Certification Prep: Validate Solutions]

Updating the homepage with access to commonly used reports is the best way to make sure the user can quickly accessthe reports they need. This could include making the global search bar bigger on every page, adding the daily task component to the homepage, or creating a mind board to communicate the visual style of the UI. Additionally, Salesforce has some great resources on designing for search, such as their Search Design Guide [1] and their Search Best Practices [2].
[1] https://www.salesforce.com/content/dam/web/en_us/www/documents/salesforce-search-design-guide.pdf [2]

A human-centered design process is a creative approach to solving people’s problems that begins with identifying their needs and ends with creating solutions that meet those needs1. A human-centered design process typically involves the following steps in this order23:
* Observation: This step involves researching and understanding the users, their context, their goals, their
* pain points, and their behaviors. Observation methods include interviews, surveys, ethnography, contextual inquiry, and data analysis.
* Ideation: This step involves generating and exploring a wide range of possible solutions that address the users’ needs and problems. Ideation methods include brainstorming, sketching, mind mapping, affinity diagramming, and storyboarding.
* Prototyping: This step involves creating and testing low-fidelity or high-fidelity representations of the proposed solutions, such as mockups, wireframes, or interactive models. Prototyping methods include paper prototyping, digital prototyping, and rapid prototyping.
* User Feedback: This step involves collecting and analyzing feedback from the users on the prototypes, such as their opinions, preferences, satisfaction, and suggestions. User feedback methods include usability testing, user testing, focus groups, and surveys.
* Iteration: This step involves refining and improving the prototypes based on the user feedback, and repeating the prototyping and user feedback steps until the optimal solution is achieved. Iteration methods include agile development, design sprints, and A/B testing.
* Implementation: This step involves deploying and launching the final solution to the users, and monitoring and evaluating its performance and impact. Implementation methods include release management, change management, and analytics.
References: Relationship Design – Trailhead, Human-Centered Design: Definition and Stages – Interaction Design Foundation, Human-Centered Design Process – Salesforce UX The order in which CK’s UX Designer should undertake the steps of the human-centered design process to achieve maximum impact is Observation > Ideation > Prototyping > User Feedback > Iteration > Implementation. This allows the designer to take into account the user’s preferences and needs from the very beginning, as well as provide the user with feedback throughout the entire process. The order of steps for a human-centered design process is as follows:
* Observation: Observing user behaviour and interactions to gain insights into their needs and preferences.
* Ideation: Coming up with ideas for potential solutions based on the insights from the observation phase.
* Prototyping: Creating a prototype of the potential solution to test out with users.
* User Feedback: Gathering feedback from users on the prototype and making changes based on their feedback.
* Iteration: Iterating on the prototype based on the feedback from users.
* Implementation: Implementing the final solution.
For more information on the human-centered design process, please see the following Salesforce documentation: https://trailhead.salesforce.com/en/content/learn/modules/ux_design_process

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)

Explanation
The two UX design principles that are key to creating excellent mobile user experiences are:
Consistency across device experiences. This means that the design of a mobile app or website should match the design of the desktop version, as well as other platforms and devices. Consistency helps users to recognize and trust the brand, as well as to navigate and use the product more easily. Consistency also reduces the cognitive load and confusion for users who switch between different devices12 Prioritization of content and UI elements on the screen. This means that the design of a mobile app or website should focus on the most important and relevant information and actions for the user, and eliminate or minimize the unnecessary or secondary ones. Prioritization helps users to achieve their goals faster and more efficiently, as well as to avoid distractions and clutter. Prioritization also improves the readability and usability of the product on smaller screens34 References: [Mobile UX Design: The Comprehensive Guide – updated 2023], [Mobile UX design principles and best practices], [Mobile UX Design: The Ultimate Guide 2023 – Bluespace], [Mobile UX Design: Key Principles. by Nick Babich – UX Planet]
https://uxcam.com/blog/mobile-ux/ https://uxplanet.org/mobile-ux-design-key-principles-dee1a632f9e6

Explanation
The human-centered design approach is a problem-solving technique that puts real people at the center of the development process, enabling designers to create products and services that resonate and are tailored to the audience’s needs. The human-centered design approach typically involves four stages: clarify, ideate, develop, and implement1. The first stage, clarify, is dedicated to collecting data and observing the users to clarify the problem and how to solve it. Rather than developing products based on assumptions, designers conduct user research and assess user needs to determine what the users want. The clarify stage requires empathy-the capability of understanding another person’s experiences and emotions. Designers need to consider the users’ perspectives and ask questions to determine what products they’re currently using, why and how they’re using them, and the challenges they’re trying to solve2.
Therefore, the activity that should come first in the human-centered design process is observing the medical staff while they use their existing portal. This activity will help the UX designer to understand the context, the goals, the pain points, and the preferences of the medical staff, as well as to identify the opportunities for improvement and innovation. The other activities, such as estimating the cost, writing technical requirements, and designing a mockup, belong to the later stages of the human-centered design process, after the problem and the user needs have been clearly defined.
References: What is Human-Centered Design? – updated 2023 | IxDF and What Is Human-Centered Design?
| HBS Online
The first activity inthe process when using a human-centered design approach to redesign a portal that medical staff use to report on patient demographics should be observing the medical staff while they use their existing portal. This is a critical step in the process, as ithelps to identify user needs, preferences, and behaviors so that the design of the new portal can be tailored to meet their specific needs.
Observing the medical staff while they use the portal will help to identify any existing problems and highlightareas where the portal can be improved. This can include issues with usability, functionality, and accessibility. Additionally, observing how the medical staff interact with the portal can help to identify any potential areas of improvement and uncover anyhidden requirements or user needs.
References:
[1] https://www.salesforce.com/blog/2019/02/human-centered-design.html [2] https://uxplanet.org/human-center

Explanation
CK’s customers can engage in the following three ways using the out-of-box functionality of Experience Cloud:
Endorsement of skills and expertise: Customers can endorse each other’s skills and expertise on their profiles, which helps to build trust and credibility within the community.
Join affinity groups: Customers can join groups based on their interests, preferences, or needs, which allows them to connect with like-minded people and share relevant information.
Recognize peers with badges: Customers can recognize each other’s contributions and achievements by awarding badges, which helps to motivate and appreciate the community members. References:
1: Endorse Skills and Expertise
2: Create and Manage Groups
3: Award Badges to Recognize Members

A deal closer is someone who is responsible for closing sales deals with prospects and customers. They need to update existing prospect and customer records to keep track of their interactions and status. They also need to log activities such as calls, emails, and notes to document their communication and follow-ups. They also need to review and work through their list of leads or opportunities to prioritize their tasks and identify the best prospects to focus on. These activities are essential for a deal closer to manage their pipeline and achieve their sales goals. Creating cases from issues and customizing and administering Salesforce are not activities that a deal closer would do each day. These are more likely to be done by a customer service agent or a Salesforce administrator, respectively. References: [Salesforce Certified User Experience Designer Exam Guide], [UX Designer Certification Prep: User Research], [UX Designer Certification Prep: User Roles and Personas]

Explanation
Two best practices that should be considered when using a custom Lightning component to fulfill a specific business requirement are:
Find the closest Salesforce Lightning Design System (SLDS) Blueprint to help inform the custom Lightning component. The SLDS is a collection of design guidelines, UI components, and code samples that help you create consistent and beautiful user interfaces for Lightning applications. The SLDS Blueprints are examples of common UI patterns and components that are built with the SLDS and follow the design principles and best practices. The Blueprints can help you inform the custom Lightning component by providing inspiration, guidance, and code snippets that you can modify and reuse. The Blueprints can also help you ensure that the custom Lightning component is compatible and consistent with the rest of the Lightning application and the Salesforce platform. [UX Designer Certification Prep: Salesforce Design System], Lightning Design System Website Exhaust the list of available base Lightning components in the Component Library. The base Lightning components are a set of pre-built UI components that you can use to create custom Lightning components. The base Lightning components are built with the SLDS and provide the functionality and interactivity that you need for common UI elements, such as buttons, icons, forms, tables, charts, and more. The base Lightning components also handle the accessibility, security, and performance aspects for you, so you don’t have to worry about them. The Component Library is a reference guide that provides documentation and examples for the base Lightning components, as well as other Lightning web components and Aura components. The Component Library can help you explore the list of available base Lightning components and see how they work and how to use them. The Component Library can also help you avoid reinventing the wheel and save time and effort by using the base Lightning components as much as possible, and only creating custom Lightning components when there is no suitable base Lightning component for your requirement. [UX Designer Certification Prep: User Testing and Evaluation], Developer Center’s Lightning Component Library Prioritizing Aura markup even if there is a Lightning Web Component (LWC) available, and creating HTML markup and linking the SLDS stylesheet via static resource are not best practices that should be considered when using a custom Lightning component to fulfill a specific business requirement. These practices can lead to suboptimal performance, maintainability, and compatibility issues for the custom Lightning component.
Aura markup is the older syntax for creating Aura components, which are the predecessor of Lightning web components. Lightning web components are the newer and faster way of creating custom UI components for Lightning applications, using modern web standards and best practices. Lightning web components also have better interoperability and compatibility with Aura components and other web components, as well as with the base Lightning components and the SLDS. Therefore, it is recommended to use Lightning web components over Aura components whenever possible, and to use LWC markup instead of Aura markup for creating custom Lightning components. [UX Designer Certification Prep: User Testing and Evaluation], Lightning Web Components Developer Guide Creating HTML markup and linking the SLDS stylesheet via static resource is also not a recommended practice for creating custom Lightning components, because it can create unnecessary complexity and duplication for the custom Lightning component. A static resource is a file or a collection of files that can be referenced by a Lightning component, such as images, style sheets, JavaScript libraries, or fonts. However, linking the SLDS stylesheet via static resource means that you have to manually download and upload the SLDS files to your org, and update them whenever there is a new version of the SLDS. This can create maintenance and compatibility issues for the custom Lightning component, as

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.
References: How to Write a Usability Testing Report (With Templates and Examples) – Xtensio, How to Report Usability Test Results for Maximum Impact | Maze, Ethical Considerations in User Research and Testing | Interaction Design Foundation (IxDF)

The best way to store the information of Cloud Kicks’ storage facilities in Salesforce is to use objects to represent storage facilities and fields to store facility details. This is because objects and fields in Salesforce are analogous to database tables and columns, respectively1. Each object contains a set of fields that store data values, and each record is an instance of an object1. Therefore, if Cloud Kicks wants to store the same information that they have in their Excel sheet, they can create a custom object called Storage Facility, and add fields for each detail that they want to track, such as location, capacity, inventory, and so on.Then, they can create records for each storage facility and populate the fields with the corresponding data. This way, they can store and manage their data in a structured and consistent way, and leverage the features and benefits of Salesforce, such as reports, dashboards, automation, and security23.
Using objects to represent facility details and fields to store storage facilities is not a valid option, as it does not make sense to use objects as data values. Objects are meant to represent entities or concepts, not attributes or properties1. Using objects to represent both storage facilities and facility details is also not a good option, as it would create unnecessary complexity and redundancy in the data model. Objects can be related to each other through various types of relationships, such as lookup, master-detail, or many-to-many4. However, in this case, there is no need to create a separate object for each facility detail, as they are not independent entities, but rather characteristics of the storage facilities. Creating a separate object for each detail would also require creating more fields, records, and relationships, which would increase the maintenance and storage costs, and reduce the performance and usability of the system5. References:
* Learn All About Objects and Fields in Salesforce – Forcetalks
* Mastering Salesforce CRM Administration – Packt Subscription
* Overview of Salesforce Objects and Fields
* Object Reference for the Salesforce Platform
* Understand Custom & Standard Objects Unit | Salesforce Trailhead

The conceptual approach of desirable, feasible, and viable describes how to evaluate design solutions based on three criteria:
* Desirable: The solution meets the needs and wants of the users and stakeholders.
* Feasible: The solution can be implemented with the available resources and technology.
* Viable: The solution can generate value and sustain itself in the market and environment. By incorporating human-centered design, CK is aiming to create design solutions that are desirable for its Sales team and customers, feasible with the Salesforce platform and tools, and viable for its business goals and strategy. References:
* [1]: UX Designer Certification Prep: Design Thinking, Unit 3: Ideate
* [2]: UX Designer Certification Prep: Design Thinking, Unit 4: Prototype and Test T-shirt sizing is a methodology that can be used to roughly estimate the work required for each item in a sprint backlog. It involves assigning a size category (such as XS, S, M, L, XL) to each item based on its complexity, effort, and uncertainty. T-shirt sizing is a relative estimation technique that allows the team to compare items and prioritize them accordingly. It is also a quick and easy way to get a high-level overview of the scope of work without getting into too much detail. References:
* [UX Designer Certification Prep: Agile UX]
* [Agile Estimation Techniques: A True Estimation in an Agile Project]

Responsive design is a web design approach that aims to make web pages adapt to different screen sizes and resolutions, ensuring good usability and user experience across all devices. Some of the best practices for responsive design are:
* Specify breakpoint sizes: Breakpoints are the points at which the layout of a web page changes based on the width of the viewport. For example, a web page may have a two-column layout on a desktop, a single-column layout on a tablet, and a stacked layout on a mobile phone. Specifying breakpoint sizes helps to create a fluid and flexible layout that responds to the device capabilities and user preferences.
Breakpoints can be specified using media queries in CSS, which allow applying different styles depending on the media features, such as width, height, orientation, resolution, etc. For example:
@media (max-width: 600px) { /* Styles for screens that are 600px or smaller */ }
@media (min-width: 601px) and (max-width: 900px) { /* Styles for screens that are between 601px and
900px */ }
@media (min-width: 901px) { /* Styles for screens that are 901px or larger */ }
* Minimize page weight: Page weight is the amount of data that a web page transfers to load on a browser.
It includes the size of the HTML, CSS, JavaScript, images, fonts, and other resources that make up the web page. Minimizing page weight helps to improve the performance, speed, and user satisfaction of a web page, especially on mobile devices that may have limited bandwidth, battery, and processing power. Some of the ways to minimize page weight are:
* Optimize images: Images are often the largest contributors to page weight, so it is important to optimize them for the web. This means choosing the right format, size, resolution, and compression level for each image, as well as using responsive images techniques, such as the srcset and sizes attributes, to deliver the most appropriate image for each device and screen size.
* Implement caching: Caching is a technique that stores a copy of a web page or its resources on the browser or the server, so that they can be reused without having to be downloadedagain. This reduces the amount of data that needs to be transferred and improves the loading time of a web page. Caching can be implemented using HTTP headers, such as Cache-Control and Expires, or using service workers, which are scripts that run in the background and intercept network requests.
* Minify and concatenate files: Minification is a process that removes unnecessary characters, such as whitespace, comments, and formatting, from the code files, such as HTML, CSS, and JavaScript, to reduce their size. Concatenation is a process that combines multiple code files into one, to reduce the number of HTTP requests that the browser needs to make. Both minification and concatenation can help to reduce the page weight and improve the performance of a web page.
* Use a content delivery network (CDN): A CDN is a network of servers that are distributed across different locations and regions, and that store and deliver copies of a web page or its resources to the users. A CDN can help to reduce the page weight and improve the speed of a web page by serving the content from the nearest server to the user, reducing the latency and bandwidth consumption.
The other two options, using separate URLs per device and utilizing pop-up windows, are not considered responsive design best practices, as they can create usability and accessibility issues for the users. Using separate URLs per device means creating different versions of a web page for different devices, such as example.com for desktop, m.example.com for mobile, and t.example.com for tablet. This approach can lead to inconsistent and fragmented user experiences, as well as duplicate content and SEO problems. Utilizing pop-up windows means creating new browser windows that open on top of the current web page, usually to display advertisements, notifications, or forms. This approach can be annoying and intrusive for the users, as well as difficult to close or navigate on small screens.
References: Responsive Design: Best Practices and Considerations | Toptal, Responsive design – Learn web development | MDN, The Beginner’s Guide to Responsive Web Design in 2023 – Kinsta, Responsive Design Best Practices. by Nick Babich – UX Planet

Human-centered design is a practice where designers focus on people and their context, and seek to understand and solve the right problems for them. Human-centered design involves the following elements1:
* Empathy. Designers need to genuinely care about the people they design for, and build empathy by immersing themselves in the community that will use their products or services.
* Creativity. Designers need to find creative ways to solve users’ problems, and generate multiple ideas and prototypes that can be tested and refined.
* Business needs. Designers need to make their products or services commercially successful, and align them with the goals and values of the organization.
To incorporate human-centered design across its organization, Cloud Kicks should adopt the following two practices:
* Observing user behavior. Designers should conduct user research and communicate with their users regularly, to understand their needs, motivations, challenges, and goals. Observing user behavior can help designers to identify the pain points and opportunities for improvement, and to validate their assumptions and hypotheses.
* Putting oneself in the situation of the end user. Designers should empathize with their users, and try to see the world from their perspective. Putting oneself in the situation of the end user can help designers to create products or services that are relevant, useful, and desirable for them.
The following two practices are not aligned with human-centered design, and should be avoided:
* Including innovative ideas to showcase technology. Designers should not prioritize technology over people, and should not include features or functions that are not necessary or beneficial for the users.
Including innovative ideas to showcase technology can lead to products or services that are complex, confusing, or frustrating for the users.
* Creating requirements based on business leaders’ priorities. Designers should not ignore the voice of the users, and should not create products or services that only satisfy the business needs. Creating requirements based on business leaders’ priorities can lead to products or services that are irrelevant, useless, or undesirable for the users.
References: Human-Centered Design: An Introduction, Practices, and Principles – Shopify