Explanation

When building custom Lightning components, Salesforce emphasizes efficiency, consistency, and performance. Designers and developers should first leverage existing base components to avoid unnecessary custom work. For truly custom needs, reference SLDS Blueprints for validated patterns that ensure visual and functional alignment with Lightning Experience, promoting accessibility and maintainability.

✅ Correct Option: B - Find the closest Salesforce Lightning Design System (SLDS) Blueprint to help inform the custom Lightning component.
SLDS Blueprints provide framework-agnostic HTML, CSS, and guidelines for common UI patterns. Starting with the nearest blueprint accelerates development, ensures consistency with native Salesforce styling, and incorporates best practices for accessibility and responsiveness—ideal guidance when creating custom components from scratch.

✅ Correct Option: D - Exhaust the list of available base Lightning component in the component Library.
Salesforce's Component Library offers numerous pre-built, optimized base components (e.g., lightning-card, lightning-input). Checking these first prevents reinventing common functionality, reduces development time, ensures performance and accessibility, and maintains a native look-and-feel before resorting to fully custom solutions.

❌ Incorrect Option: A - Prioritize Aura markup even if there is a Lightning Web Component (LWC) available.
Salesforce recommends Lightning Web Components (LWC) over Aura for new development due to better performance, modern web standards alignment, and easier maintenance. Prioritizing the older Aura framework contradicts current guidelines and misses LWC's advantages in speed and developer productivity.

❌ Incorrect Option: C - Create HTML markup and link the SLDS stylesheet via static Resource.
In Lightning components (especially LWC), SLDS styles are automatically available—no need for manual static resource uploads. This outdated Visualforce-era approach adds unnecessary complexity, risks version mismatches, and bypasses built-in optimizations like scoped styling and design tokens.

Summary
Always check base components first (D) and use SLDS Blueprints (B) for custom builds to align with Salesforce standards. Avoid legacy Aura prioritization or manual SLDS linking for modern efficiency. These practices promote faster, consistent, and high-quality UX in Lightning.

Reference:
Lightning Web Components Developer Guide - Create a Component from an SLDS Blueprint

Explanation

A B2B sales portal is an external website where business customers can log in to view products, place orders, check order history, and manage their account. The key requirement is seamless integration with CRM data (accounts, contacts, opportunities, orders) to provide a personalized, self-service experience.

Correct Option: (B) Experience Cloud
This is correct. Experience Cloud is Salesforce's platform for building branded digital experiences (portals, websites, apps) for external audiences. It natively integrates with CRM data in Sales Cloud, allowing the designer to create a secure, authenticated B2B portal where customers can directly interact with their own Salesforce data.

Incorrect Options

(A) Commerce Cloud
This is incorrect. Commerce Cloud is a specialized platform for building B2C and B2B digital storefronts and e-commerce experiences, focused on product catalogs, shopping carts, and checkout. While it can integrate with CRM, it is overkill for a portal focused on CRM integration and sales relationship management rather than a full online store.

(C) Sales Cloud
This is incorrect. Sales Cloud is the internal CRM application used by Cloud Kicks' own sales team to manage leads, opportunities, and accounts. It is not a tool for building external-facing portals for customers. Experience Cloud is the solution that extends and presents Sales Cloud data to external users.

📝 Summary
To build a B2B sales portal deeply integrated with CRM, use Experience Cloud. It is the dedicated Salesforce solution for creating secure, customized websites that connect external partners and customers directly to their relevant Sales Cloud data and processes.

🔗 Reference
• Salesforce Help: Experience Cloud – Overview of building external portals and sites with Experience Cloud.

Explanation

Mobile design requires a "mobile-first" mindset, focusing on the unique constraints of smaller screens and touch interactions. Designers must ensure that the transition between desktop and mobile is seamless while acknowledging that mobile users often have different immediate needs and environmental distractions compared to desktop users.

✅ Correct Option: Option C
Consistency is vital because users often switch between devices to complete a single journey. Providing a familiar interface, terminology, and branding across both desktop and mobile reduces the learning curve and builds trust. When the experience is consistent, users don't have to re-learn how to navigate your application when they change hardware.

✅ Correct Option: Option D
Due to limited screen real estate, designers must prioritize the most critical content and actions. This involves "progressive disclosure"—showing only what is necessary for the current task and hiding secondary information. Prioritization ensures that the user's primary goal is always front and center, preventing the interface from becoming cluttered or overwhelming.

❌ Incorrect Option: Option A
Removing all images is an extreme and incorrect approach to performance. While optimizing image size is important for load times, images often provide essential context, branding, and visual cues. A total removal would degrade the user experience and make the interface less engaging and harder to navigate for the user.

❌ Incorrect Option: Option B
Increasing the need for typing is a major UX anti-pattern for mobile. Onscreen keyboards are prone to errors and take up significant screen space. Excellent mobile design aims to minimize typing by using picklists, checkboxes, and auto-population, making data entry as effortless as possible for the user.

📝 Summary
Consistency ensures a unified brand and functional experience across all platforms.
Prioritization helps users focus on the most important tasks by managing limited space effectively.
These principles together create a mobile experience that is both intuitive and highly efficient.

🔗 Reference
Salesforce Help: Mobile UX Design Best Practices

Explanation

SLDS provides structured ways to ensure uniform visuals across components and pages. While blueprints guide full component construction and BEM helps with naming conventions, low-level foundational consistency in layout elements like grids, alignments, spacing, and typography comes from dedicated reusable classes designed specifically for these purposes.

✅ Correct Option: C. Utility Classes
Utility classes in SLDS are single-purpose CSS helpers (e.g., slds-grid for layouts, slds-m-around_medium for spacing, slds-text-align_center for alignment, slds-text-heading_large for typography). They allow quick, consistent application of these styles without custom CSS, maintaining visual harmony across custom and base components.

❌ Incorrect Option: A. Component Blueprints
Blueprints provide HTML markup, CSS, and guidelines for building complete UI components (like buttons or cards). They ensure consistency within specific components but are not the primary tool for general alignments, grids, spacing, or typography across arbitrary elements.

❌ Incorrect Option: B. BEM Naming Classes
BEM (Block-Element-Modifier) is the naming convention used throughout SLDS for readable, modular class names (e.g., slds-button_neutral). It supports maintainable code structure but does not directly provide styles for grids, spacing, alignment, or typography.

Summary
Utility classes handle foundational styling like grids, spacing, alignment, and typography for broad consistency. Component blueprints focus on full UI patterns, not isolated layout utilities. BEM is a naming methodology, not a source of visual styling rules. Leveraging utilities promotes efficient, uniform designs aligned with Lightning Experience.

Reference:
SLDS Utilities – Grid
Style Components with Lightning Design System
SLDS Markup and Style Guidelines (BEM Naming)

Explanation:

To overcome developer pushback, the designer must foster shared ownership and provide objective, actionable evidence for the design's value, moving the conversation from subjective opinion to measurable user benefit.

✅ Correct Option: C
Work together on setting up UX Indicators is correct. Collaboratively defining success metrics (UX Indicators) shifts the focus to shared goals and measurable outcomes. It gives developers clear, objective criteria to see how the design directly impacts user success, turning feedback into data-driven collaboration.

❌ Incorrect Option: A
Share research notes from previous projects is incorrect. While research is valuable, sharing notes from previous projects lacks direct relevance and shared context for the current team and specific changes. This approach can feel disconnected and doesn't actively involve developers in the current problem-solving process.

❌ Incorrect Option: B
Get buy-in from the development lead first is incorrect. This tactic can create a top-down dynamic that may breed resentment or passive compliance rather than genuine understanding. It bypasses direct collaboration with the wider development team, failing to address their specific concerns or build shared ownership of the solution.

Summary:
The most effective method is to co-create UX Indicators. This collaborative, data-focused approach builds a shared language of success, aligns the team on user outcomes, and transforms the design rationale from opinion into objective, shared goals that developers can directly influence and support.

Reference:
Salesforce Trailhead: UX Design - Defining Success with UX Indicators