Explanation

The discovery phase in Salesforce UX projects focuses on deeply understanding user needs, business goals, and current challenges before designing solutions. Effective planning involves structured research preparation, direct user engagement for authentic insights, and a clear focus on the root problem to avoid premature solutioning, ensuring human-centered outcomes.

✅ Correct Option: B. Gather insight from end users.
Directly engaging end users through interviews, observations, or surveys uncovers real behaviors, pain points, and motivations. This empathetic approach provides qualitative data essential for creating personas, journey maps, and requirements that reflect actual usage patterns in Salesforce environments.

✅ Correct Option: C. Establish the research plan and timeline.
A well-defined plan outlines objectives, methods (e.g., interviews, shadowing), participant recruitment, and a realistic timeline with milestones. This structured strategy keeps the discovery phase organized, aligned with stakeholders, and efficient, preventing scope creep or delays.

✅ Correct Option: D. Understand the problem before moving to solutions.
Discovery prioritizes framing the problem space thoroughly—asking "why" repeatedly and validating assumptions—before ideation. Jumping to solutions risks building the wrong features; focusing here ensures designs address true user and business needs effectively.

❌ Incorrect Option: A. Consider platform-based before custom solutions.
This is a best practice during the design and implementation phases (e.g., leveraging declarative tools like Flow or SLDS components). In discovery planning, the emphasis is on research and problem understanding, not yet evaluating solution types.

❌ Incorrect Option: E. Determine user acceptance criteria.
Defining acceptance criteria or success metrics typically occurs after discovery, during requirements refinement or testing planning. Discovery focuses on exploration and insight gathering, not final validation benchmarks.

Summary
Gather end-user insights for empathy-driven requirements. Create a clear research plan and timeline for structured execution. Fully understand the problem to guide meaningful solutions. These foundational practices set up successful, user-centered Salesforce UX projects.

Reference:
Learn About Discovery
UX Basics – Discovery and Research
Get to Know the Salesforce Designer Role

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:

🟢 Correct Option: A. Responsive
Responsive design ensures that websites adapt seamlessly to different devices, screen sizes, and orientations. By using flexible layouts, images, and CSS media queries, the design adjusts dynamically to maintain usability across desktops, tablets, and mobile devices. This approach provides a consistent user experience regardless of how or where the site is accessed.

🔴 Incorrect Option: B. Refactored
Refactoring means restructuring code or design for efficiency and maintainability. While important for technical improvements, it does not specifically address adapting content to different screen sizes or devices. It is a development-focused term, not a user experience design method.

🔴 Incorrect Option: C. Reactive
Reactive design refers to systems or interfaces that respond to user actions or changes in data in real time. While useful in interaction design, it does not describe the concept of adapting layouts to devices and orientations. Thus, it does not apply to the scenario described.

🔴 Incorrect Option: D. Proactive
Proactive design refers to anticipating user needs and providing solutions before they are requested. While valuable in UX strategy, it is unrelated to layout responsiveness or device adaptability. It focuses more on predictive design, not structural adaptation.

📝 Summary
The scenario requires the website to adapt to different devices and orientations, which is the core principle of responsive design. Unlike reactive or proactive strategies, responsive design directly addresses flexible layouts and scalability. It ensures accessibility and usability across all platforms without requiring separate designs for each device.

📘 Reference
Salesforce Lightning Design System – Responsive Design

Explanation

On mobile devices, screen space is limited, and users often interact with one hand while scrolling. Accordions help manage content density, but poor implementation can frustrate users. Best practices focus on keeping headings visible for context, limiting open sections to reduce scrolling fatigue, and avoiding complex structures or unreliable navigation methods.

✅ Correct Option: A. Include persistent headings.
Persistent headings remain visible even when a section is expanded, providing constant context on mobile screens. This helps users stay oriented without losing sight of other section titles, especially during vertical scrolling, and improves scannability and navigation in compact views.

✅ Correct Option: D. Only allow users to open one selection at a time.
Restricting to a single open section (exclusive collapse) prevents overwhelming the limited mobile viewport with too much content at once. It reduces excessive scrolling, focuses attention on one topic, and mimics familiar patterns like native mobile menus for smoother interaction.

❌ Incorrect Option: B. Nest an accordion inside of another
Nested accordions add layers of complexity, requiring multiple taps to reach deeper content. On mobile, this increases cognitive load, interaction cost, and frustration—general UX guidelines strongly recommend avoiding nesting to maintain simplicity and clarity.

❌ Incorrect Option: C. Use the ‘’back’’ browser button to collapse content
Relying on the browser back button for collapse breaks standard web navigation expectations and can accidentally exit the page. It’s unreliable for in-page interactions and disrupts user flow, especially in Salesforce mobile apps where native controls are preferred.

Summary
Persistent headings keep context visible on small screens. Single-open sections control content overflow and scrolling. Avoid nesting or browser back for collapse to prevent confusion. These enhancements align with mobile-first UX for better accessibility and efficiency.

Reference:
Accordion Component Blueprint
Accordion Guidelines and Best Practices
Lightning Accordion Component Documentation

Explanation

When Account and Opportunity OWDs are both Private, creating owner-based sharing rules on Opportunity (e.g., “Owner’s Team shares with same Team”) automatically grants implicit Read-only access to the parent Account for those shared Opportunities. Salesforce does this to prevent users from seeing an Opportunity without its required Account context.

✅ Correct Option: C. Sales reps on the same team will have Read access to the Accounts for Opportunities owned by their team members.
Opportunity owner-based sharing rules trigger implicit Account sharing. Any sales rep who gains access to a teammate’s Opportunity automatically receives Read-only access to the related Account record, even if no explicit Account sharing rule exists. This ensures contextual integrity but widens Account visibility within the team.

❌ Incorrect Option: A. All sales reps will have Read access to Accounts for all Opportunities.
The sharing is limited only to Opportunities owned by members of the same team, not all Opportunities in the org. Therefore, Account access is granted only for those specific related Accounts, not universally.

❌ Incorrect Option: B. Sales Reps on the same team will have Edit access to the Accounts for Opportunities owned by their team members.
Implicit Account sharing from Opportunity rules is always Read-only. Edit access on the Account would require separate explicit sharing rules or manual sharing on the Account object itself.

❌ Incorrect Option: D. All sales reps will have Read access to all Accounts.
Access is scoped only to Accounts linked to the shared Opportunities within the same team. Sales reps do not gain Read access to every Account in the organization.

Summary
Owner-based Opportunity sharing rules automatically create implicit Read-only sharing on the parent Account. This side effect is intentional by Salesforce to maintain data context. Account access is limited to only those Accounts tied to the shared Opportunities within the team.

Reference:
Implicit Sharing in Salesforce
Control Access to Accounts Using Opportunity Teams
Salesforce Security Guide