Salesforce Certified User Experience Designer Practice Test - Questions Answers, Page 3

Usability testing is a type of testing that evaluates how easy and intuitive a product or service is to use by observing real users performing specific tasks. Usability testing can help the UX Designer to measure the effectiveness, efficiency, and satisfaction of the new form for the call center staff. Usability testing can also help to identify any usability issues or areas for improvement in the form design.Usability testing can be conducted in various ways, such as moderated or unmoderated, remote or in-person, qualitative or quantitative, or using various tools and methods12.Reference:

Usability Testing

Usability Testing Methods

According to the Web Content Accessibility Guidelines (WCAG), which are the leading international standards for accessible web design, perceivable content is content that can be presented to users in ways they can perceive.This means that the content should be available to the senses (vision, touch, and hearing) either through the browser or through assistive technologies like screen readers, screen enlargers, and others1. Therefore, the content should only be visible is the correct answer, as it implies that the content can be seen by users who rely on vision to access the web. The other options are incorrect, as they suggest that the content is not perceivable to all users.

Web Accessibility For Beginners | DigitalOcean, Perceivable: Content on the web should be perceivable.

The best way to ensure the end-user experience when designing a new page layout for a custom object in Salesforce is to group similar fields using sections. Sections are UI components that allow you to organize fields into logical groups and provide headings and descriptions for each group. Sections help to improve the readability, scannability, and usability of the page layout by reducing the visual clutter and providing a clear structure and hierarchy for the information. Sections also help to align the page layout with the user's mental model and expectations, as well as the business processes and workflows. [UX Designer Certification Prep: User Interface Design Principles], [UX Designer Certification Prep: Salesforce Design System]

Including all potentially useful fields is not a good way to ensure the end-user experience when designing a new page layout for a custom object in Salesforce, because it can create a crowded and overwhelming interface that is hard to navigate and understand. It can also increase the cognitive load and the scrolling effort for the user, as well as the maintenance cost for the designer. It is better to include only the essential and relevant fields that the user needs to perform their tasks and goals, and use other methods such as related lists, tabs, or modals to display additional information. [UX Designer Certification Prep: User Interface Design Principles], [UX Designer Certification Prep: Salesforce Design System]

Making field labels and API names identical is not a good way to ensure the end-user experience when designing a new page layout for a custom object in Salesforce, because it can create confusion and inconsistency for the user and the developer. Field labels are the text that appear on the user interface to identify the fields, while API names are the unique identifiers that are used by the system and the code to reference the fields. Field labels and API names should be different, because they have different purposes and audiences. Field labels should be clear, concise, and descriptive, using natural language and proper capitalization, punctuation, and spacing. API names should be concise, unique, and consistent, using underscores and camel case to separate words. [UX Designer Certification Prep: User Interface Design Principles], [UX Designer Certification Prep: Salesforce Design System]

Marking all fields as required is not a good way to ensure the end-user experience when designing a new page layout for a custom object in Salesforce, because it can create frustration and annoyance for the user, as well as increase the error rate and the abandonment rate. Required fields are fields that the user must fill in before they can save or submit the record. Required fields should be used sparingly and only for the fields that are absolutely necessary for the system or the business logic. Marking all fields as required can make the user feel pressured and constrained, and force them to enter irrelevant or inaccurate data. It can also make the user miss the truly important fields, or give up on completing the record altogether. [UX Designer Certification Prep: User Interface Design Principles], [UX Designer Certification Prep: Salesforce Design System]Reference:[UX Designer Certification Prep: User Interface Design Principles], [UX Designer Certification Prep: Salesforce Design System]

To ensure new Salesforce users are given the appropriate onboarding experience, a UX Designer should use the following two on-App Guidance customizations:

Specify prompt scheduling: This allows the designer to control when and how often the prompts appear to the users, based on criteria such as start and end dates, frequency, and snooze duration. This way, the designer can tailor the onboarding experience to the users' needs and preferences, and avoid overwhelming or annoying them with too many or irrelevant prompts.

Set prompt permissions: This allows the designer to target the prompts to specific user groups, based on profiles and permissions. This way, the designer can ensure that the prompts are relevant and useful to the users, and avoid showing them information that they do not need or have access to.

Salesforce In-App Guidance: Enhance Your User Experience

Create and Manage In-App Guidance Prompts

Einstein Bots and Automated Invitations are two Salesforce features that can boost engagement on Cloud Kicks' website. Einstein Bots are chatbots that can provide automated and personalized responses to customers' questions and requests on the website. They can also escalate complex cases to human agents, collect feedback, and provide recommendations.Einstein Bots can help Cloud Kicks to improve customer satisfaction, reduce wait times, and increase conversions1. Automated Invitations are pop-up messages that invite website visitors to start a chat or video call with a service agent. They can be triggered by various criteria, such as time spent on the website, page visited, or customer profile.Automated Invitations can help Cloud Kicks to proactively engage with potential customers, offer assistance, and generate leads2.Reference:[Einstein Bots Basics] (https://ascendix.com/blog/salesforce-sales-engagement/), [Set Up Automated Chat Invitations] (https://bing.com/search?q=Salesforce+features+to+boost+engagement)

Consequence Scanning is a workshop method that helps teams to identify and mitigate the potential positive and negative impacts of their products or services on users, society, and the environment. When conducting a Consequence Scanning workshop, two important considerations are:

Consider design ramifications to prevent misuse and protect communities: This means that teams should think beyond the intended use cases and benefits of their products or services, and also consider the possible unintended or harmful consequences that may arise from their design choices. For example, teams should ask themselves how their products or services could be misused, abused, or exploited by malicious actors, or how they could affect vulnerable or marginalized groups, or how they could contribute to environmental or social issues. By considering these design ramifications, teams can proactively address and mitigate the ethical risks and challenges that may emerge from their products or services, and protect the well-being and interests of their users and communities.

Bring together a cross-function group with varied experiences: This means that teams should involve diverse and relevant stakeholders in the Consequence Scanning workshop, such as product managers, designers, developers, researchers, testers, marketers, legal experts, ethicists, users, or representatives from affected communities. By bringing together a cross-function group with varied experiences, perspectives, and backgrounds, teams can gain a more holistic and comprehensive understanding of the potential impacts of their products or services, and avoid blind spots, biases, or assumptions that may limit their vision or judgment. A cross-function group can also foster more creative and collaborative problem-solving, and generate more inclusive and responsible solutions.

How To Run a Consequence Scanning Workshop

Consequence scanning: How to mitigate risks in your service

Incorporate Ethics by Design Concepts

A standard person account object is the best option for representing the bank's customers within its Salesforce instance. A person account is a type of account that represents an individual rather than a company. Person accounts are a hybrid of the account and contact objects, combining their characteristics into one. They allow the bank to store information that applies to humans, such as first and last names, email, phone, address, etc. When a person account is created, a contact is automatically created and associated with the account. Person accounts are the Salesforce official model for representing an individual and can be used alongside business accounts for B2B and B2C activities.In Financial Services Cloud, person accounts can be used for a simplified, customizable user experience1. A person account can also have related opportunities, which are potential sales or revenue-generating events.This way, the financial advisor can access a customer's record and see all potential business opportunities related to each individual customer2.

The other options are not suitable for the bank's scenario. A standard lead object is a prospect or potential customer who has expressed interest in the bank's products or services, but has not yet qualified as a sales opportunity.A lead can be converted into an account, a contact, and an opportunity when it is ready to be pursued3. However, the bank does not need to use leads to track its customers, as they are already existing customers who have accounts with the bank. A standard opportunity object is a sales or revenue-generating event that is related to an account. An opportunity can have multiple stages, products, amounts, and probabilities of closing.An opportunity can also be linked to a campaign, which is a marketing initiative to generate leads or contacts4. However, the bank cannot use opportunities alone to represent its customers, as they are not standalone objects, but rather depend on accounts. A standard account object is a company or organization that the bank does business with. An account can have multiple contacts, which are the people who work at the account and interact with the bank.An account can also have related opportunities, cases, activities, and other records5. However, the bank does not have any corporate or business customers at this time, so using standard accounts would not reflect the nature of its individual customers.

Convert Salesforce Business Accounts to Person Accounts, In Financial Services Cloud, Person Accounts can be used for a simplified, customizable user experience.

Person Accounts - Salesforce, Person Accounts Sales Cloud Basics Content Close Select Filters Product Area Feature Impact Edition Developer Edition Enterprise Edition Essentials Edition Professional Edition Unlimited Edition Experience Salesforce Classic Mobile Lightning Experience Done 632 Results Configure Access to Thanks Badges Set Up WDC Configure Thanks in the Chatter Publisher and Salesforce Mobile App... Build a Culture of Recognition with WDC Manage WDC Enable or Disable WDC Settings WDC Editions and Permissions Skills Limitations Skills Customization Recommended WDC Profiles Recommended WDC Permission Sets Enable WDC Features Configure WDC Assign WDC Only User Licenses Assign WDC Licenses Configure WDC Features Assign a WDC Administrator Create a Support Case Considerations for Setting Up WDC Thanks and Skills Features Assign Publisher Layout to Profiles Assign WDC User Feature Licenses Assign WDC Profiles Assign WDC Permission Sets Endorse a Skill Via Record Detail Pages Add a Skill Via Record Detail Pages Remove a Skill Via Record Detail Pages Schedule Reminders to Update Opportunities View a List of the Accounts or Opportunities in Your Territories Things to Know About Enterprise Territory Management Territory Type Priority Optimizing Your Territory Model Continuously Designing Territory Models Territory Model Managing Territories Enterprise Territory Management Concepts Planning and Managing Territories Territory Model State Territory Type Territory Hierarchy Bird's-Eye View of Planning and Managing Territories Report on Territories with Assigned Users Report on Territories Without Assigned Accounts Run Assignment Rules for a Territory Reporting on Territories Report on Users Not Assigned to Territories Report on Summarizable Account Fields by Territory Enterprise Territory Management Identify Territory Users by Territory Role Territory Run the Opportunity Territory Assignment Filter Preview Territory Assignments for Accounts Report on Accounts Assigned to Territories Manage Territories with Enterprise Territory Management View and Manage Assignment Rules at the Territory Model Level Enterprise Territory Management: What's Different or Not Available... Show Your Reps Other Users Assigned to Their Leads' Territories Enable Features for Enterprise Territory Management Maintain Enterprise Territory Management Find Out Which Territories an Assignment Rule Applies To Enable Enterprise Territory Management Report on the Accounts and Opportunities in Your Territories Explore Your Company's Territory Model Identify Users in Territories Assigned to Accounts Enable Filter-Based Opportunity Territory Assignment Identify an Account's Sales Territories Disable Enterprise Territory Management How Account Assignment Rules Work How Do Permissions for Territories Affect Feature and Data Access? Requirements for Assigning Opportunities to Territories Manually Assigning Opportunities to Territories Manually Delete a Territory Model Create a Territory Model Record Preparing Sales Management for Territory Reporting Setting Up and Managing Territory Assignments Define Default User Access for Territory Records

Account | Object Reference for the Salesforce Platform | Salesforce ..., Account | Object Reference for the Salesforce Platform | Salesforce Developers Object Reference for the Salesforce Platform English Pages Winter '24 (API version 59.0) Summer '23 (API version 58.0) Spring '23 (API version 57.0) Winter '23 (API version 56.0) Summer '22 (API version 55.0) Spring '22 (API version 54.0) Winter '22 (API version 53.0) Summer '21 (API version 52.0) Spring '21 (API version 51.0) Winter '21 (API version 50.0) Summer '20 (API version 49.0) Spring '20 (API version 48.0) Winter '20 (API version 47.0) Summer '19 (API version 46.0) Spring '19 (API version 45.0) Winter '19 (API version 44.0) Summer '18 (API version 43.0) Spring '18 (API version 42.0) Winter '18 (API version 41.0) Summer '17 (API version 40.0) Spring '17 (API version 39.0) Winter '17 (API version 38.0) Summer '16 (API version 37.0) Spring '16 (API version 36.0) Winter '16 (API version 35.0) Summer '15 (API version 34.0) Spring '15 (API version 33.0) Winter '15 (API version 32.0) Summer '14 (API version 31.0) Spring '14 (API version 30.0) j Overview of Salesforce Objects and Fields Reference Associated Objects (Feed, History, OwnerSharingRule, Share, and ChangeEvent Objects) Custom Objects Object Interfaces Standard Objects AcceptedEventRelation Account AccountBrand AccountContactRelation AccountCleanInfo AccountContactRole AccountInsight AccountOwnerSharingRule AccountPartner AccountRelationship AccountRelationshipShareRule AccountShare AccountTag AccountTeamMember AccountTerritoryAssignmentRule AccountTerritoryAssignmentRuleItem AccountTerritorySharingRule AccountUserTerritory2View ActionCadence ActionCadenceRule ActionCadenceRuleCondition ActionCadenceStep ActionCadenceStepTracker ActionCadenceStepVariant ActionCadenceTracker ActionCdncStpMonthlyMetric ActionLinkGroupTemplate ActionLinkTemplate ActionPlan ActionPlanItem ActionPlanTemplate ActionPlanTemplateItem ActionPlanTemplateItemValue ActionPlanTemplateVersion ActiveFeatureLicenseMetric ActivePermSetLicenseMetric ActiveProfileMetric ActiveScratchOrg ActivityHistory ActivityMetric ActivityUsrConnectionStatus AdAvailabilityDimensions AdAvailabilityJob AdAvailabilityViewConfig AdBuyServerAccount AdCreativeSizeType AdDigitalAvailability AdditionalNumber Address AdLinearAvailability AdOpportunity AdOrderItem AdOrderItemCreativeSizeType AdOrderLineAdTarget AdPageLayoutType AdProductTargetCategory AdQuote AdQuoteLine AdQuoteLineCreativeSizeType AdQuoteLineAdTarget AdServer AdServerAccount AdServerUser AdSpaceCreativeSizeType AdSpaceGroupMember AdSpaceSpecification AdSpecMediaPrintIssue AdTargetCategory AdTargetCategorySegment AgentWork AgentWorkSkill AIApplication AIApplicationConfig AIInsightAction AIInsightFeedback AIInsightReason AIInsightValue AiModelLanguage AIRecordInsight AllowedEmailDomain AlternativePaymentMethod AnalyticsLicensedAsset Announcement ApexClass ApexComponent ApexLog ApexPage ApexPageInfo ApexTestQueueItem ApexTestResult ApexTestResultLimits ApexTestRunResult ApexTestSuite ApexTrigger ApexTypeImplementor AppAnalyticsQueryRequest AppDefinition AppExtension ApplicationFormTemplate AppMenuItem AppointmentAssignmentPolicy AppointmentScheduleAggr

Lead | Object Reference for the Salesforce Platform | Salesforce ..., Lead | Object Reference for the Salesforce Platform | Salesforce Developers Object Reference for the Salesforce Platform English Pages Winter '24 (API version 59.0) Summer '23 (API version 58.0) Spring '23 (API version 57.0) Winter '23 (API version 56.0) Summer '22 (API version 55.0) Spring '22 (API version 54.0) Winter '22 (API version 53.0) Summer '21 (API version 52.0) Spring '21 (API version 51.0) Winter '21 (API version 50.0) Summer '20 (API version 49.0) Spring '20 (API version 48.0) Winter '20 (API version 47.0) Summer '19 (API version 46.0) Spring '19 (API version 45.0) Winter '19 (API version 44.0) Summer '18 (API version 43.0) Spring '18 (API version 42.0) Winter '18 (API version 41.0) Summer '17 (API version 40.0) Spring '17 (API version 39.0) Winter '17 (API version 38.0) Summer '16 (API version 37.0) Spring '16 (API version

The designer should consider the traits similar to customer personas when selecting users for testing. Customer personas are fictional representations of the target users of a product or service, based on user research and data. Customer personas help the designer to understand the needs, goals, behaviors, and preferences of the users, as well as their pain points and challenges. Customer personas also help the designer to empathize with the users and design solutions that meet their expectations and requirements. [UX Designer Certification Prep: User Research], [UX Designer Certification Prep: User Roles and Personas]

When selecting users for testing, the designer should aim to recruit users who match the traits of the customer personas as closely as possible. This ensures that the users who participate in the testing are representative of the actual or potential users of the product or service, and that the feedback and insights gathered from the testing are valid and reliable. Selecting users who have traits similar to customer personas also helps the designer to evaluate the usability and user experience of the product or service from the user's perspective, and to identify and prioritize the areas for improvement. [UX Designer Certification Prep: User Research], [UX Designer Certification Prep: User Testing and Evaluation]

Traits dissimilar to customer personas, traits similar to friends and family, and traits of the most common demographic and ability are not criteria that the designer should consider when selecting users for testing. These criteria can lead to biased or inaccurate results, as they do not reflect the diversity and complexity of the user population. Users who have traits dissimilar to customer personas may not have the same needs, goals, or expectations as the target users, and may provide feedback that is irrelevant or misleading. Users who have traits similar to friends and family may not be objective or honest in their feedback, and may have a different level of familiarity or expertise with the product or service than the target users. Users who have traits of the most common demographic and ability may not account for the variations and differences among the target users, and may exclude or marginalize the users who have special needs or preferences. [UX Designer Certification Prep: User Research], [UX Designer Certification Prep: User Testing and Evaluation]Reference:[UX Designer Certification Prep: User Research], [UX Designer Certification Prep: User Roles and Personas], [UX Designer Certification Prep: User Testing and Evaluation]

The Salesforce Lightning Design System (SLDS) provides component blueprints that will ensure consistency for Cloud Kicks' functional components. Component blueprints are ready-to-use HTML and CSS UI elements that provide the foundation for Salesforce experience development. They follow the design guidelines, accessibility standards, and best practices of Lightning Experience. They also include variants, states, and modifiers to handle different use cases and scenarios. By using component blueprints, Cloud Kicks can create functional components that are consistent with the look and feel of Lightning Experience without writing custom code or CSS.Reference:

Component Blueprints

Introduction to the Salesforce Lightning Design System