Explanation:

In Experience Cloud, escalating a question (which is a type of FeedItem or Chatter post) to a support case can be done either through manual intervention or by automating the process based on defined business logic.

A. Manually by a moderator selecting ‘’Escalate to Case’’ in the Feed:
This is a standard, out-of-the-box feature. Users with the appropriate permissions (like community moderators or internal experts) can view a question in a Chatter feed and use the "Escalate to Case" action. This manually triggers the creation of a new Case record, linking it to the original question for context.

D. Automatically via process Builder by meeting specified criteria:
For a more scalable and proactive approach, you can use automation tools like Process Builder (or its modern equivalent, a Flow triggered by Process Builder). You can define criteria for a question (e.g., it contains a specific keyword, it has no replies after 24 hours, it was posted in a high-priority group) that, when met, automatically trigger an action to create a Case record. This ensures critical questions are never missed.

Why the Other Options are Incorrect
B. Manually by users commenting ‘’Escalate’’:
This is not a standard or supported functionality. A simple comment with the word "Escalate" is just text and does not trigger any automated process or action within Salesforce to create a case. The escalation must be initiated through the dedicated UI action or a defined automation.

C. Automatically via Case Assignment Rules:
This option is incorrect because it puts the cart before the horse. Case Assignment Rules run after a Case record has already been created. Their purpose is to assign ownership of the case (e.g., to a specific user or queue), not to create the case itself from a question. The case must first be created by another method (like Option A or D) before assignment rules can act upon it.

Reference
Salesforce Help: Escalate a Question to a Case
This documentation details the manual process for moderators to escalate a question. For automation, the help documentation on Process Builder and Flows explains how they can be used to create records (like a Case) when certain conditions on a parent record (like a FeedItem) are met.

Explanation:

For a high-performance partner site that includes multiple custom components and near real-time updates, the best choice is the Build Your Own (LWR) template. LWR stands for Lightning Web Runtime, a modern, lightweight framework optimized for speed, flexibility, and custom development using Lightning Web Components (LWC).
This template is ideal for scenarios where performance is critical and the site needs to support custom, dynamic, and interactive content. Since Insightopia plans to display real-time insights and trends, LWR’s optimized rendering and minimal overhead make it the best fit. It supports advanced caching, lazy loading, and efficient component rendering — all of which contribute to faster load times and a smoother user experience.
Additionally, LWR templates are highly customizable and allow developers to build pixel-perfect UIs while still leveraging Salesforce data and security. This makes it ideal for partner-facing portals where branding, performance, and interactivity are top priorities.

❌ Incorrect Option: A. Partner Central
Partner Central is a preconfigured template designed for quick setup of partner relationship management (PRM) use cases. It includes built-in components for lead distribution, deal registration, and partner onboarding. While it’s great for out-of-the-box functionality, it’s not optimized for high-performance or real-time custom components.
Partner Central is built on the Aura framework, which is heavier and less performant than LWR. It’s best suited for standard B2B collaboration, not for highly customized, insight-driven dashboards or real-time data delivery. For Insightopia’s needs, it would be too rigid and potentially slower.

❌ Incorrect Option: B. Customer Account Portal
The Customer Account Portal template is tailored for B2C scenarios, where customers log in to view and manage their own data — such as cases, orders, or billing. It’s optimized for self-service and account management, not for partner collaboration or high-performance dashboards.
While it supports some customization, it’s not built with the same performance-first architecture as LWR. It also lacks the flexibility needed for building complex, real-time insights and custom components. Therefore, it’s not the right fit for Insightopia’s partner-focused use case.

❌ Incorrect Option: D. Help Center
The Help Center template is designed for public self-service use cases. It’s ideal for knowledge base browsing, case submission, and FAQ access. It’s not intended for authenticated partner collaboration or real-time data delivery.
Help Center sites are typically content-heavy and optimized for search and accessibility, not for dynamic dashboards or custom component integration. It also lacks the extensibility and performance tuning capabilities that LWR provides. As such, it’s not suitable for Insightopia’s partner portal vision.

📘 References
Salesforce Developer Guide: LWR Sites for Experience Cloud
Salesforce Help: Build and Customize Your Experience Cloud Site
Arrify Blog: Salesforce Experience Cloud Templates Overview

Explanation:

When you create a public Experience Cloud site, Salesforce automatically performs a number of setup actions to manage guest user access.

A. Creation of a guest role: A role is automatically created for the guest user to facilitate sharing via the role hierarchy. While roles are typically for authenticated users, a guest role is created to ensure data can be shared with the guest user via sharing rules, which is necessary for a public site.
C. Creation of a guest profile: A dedicated guest user profile is automatically created to define the permissions for unauthenticated users accessing the public site. This profile controls which objects, fields, and pages the guest user can see.
E. Creation of a guest user record: A special guest user record is automatically created and assigned to the guest profile. This record acts as the user for anyone who is not logged in, and it's what you use to configure site-wide access and sharing.

Why other options are incorrect
B. Creation of moderation criteria that are applied only to guest users: Moderation criteria are not created automatically. These are custom settings that an administrator must configure manually to manage content on the site.
D. Creation of sharing mechanisms that are available only to guest users: While a guest user's profile and record are created, and sharing rules can be used to grant them access, the specific sharing mechanisms themselves are not automatically created. The admin must set up sharing rules to grant guest users access to specific records.

Explanation:

Why:
BC wants to deliver personalized experiences across multiple audiences (providers, vendors/installers, patients) while adhering to industry standards and compliance-driven workflows. Lightning Bolt solutions are designed exactly for this evaluation: they package industry-specific templates, pages, data/config, and business process flows that you can adopt or tailor—letting you start from proven best practices rather than building from scratch. This accelerates delivery and helps stay aligned with regulated processes.

Eliminate the others:
B. Community Connect — Not the evaluation focus for industry best-practice process packs; Lightning Bolt solutions address that need directly.
C. Digital Experience framework — Choosing between LWR/Aura/Visualforce is a technical build decision, not a catalog of industry process templates. Salesforce
D. SDLC for Experiences — Good engineering hygiene, but SDLC is a generic software process, not a repository of compliant, industry-ready site patterns.

Implementation tip:
Search AppExchange and partner catalogs for Bolt solutions in healthcare and field services (e.g., provider/patient portals, vendor onboarding) and evaluate security/compliance notes, data model fit, and extensibility before selection.

Explanation:

Salesforce PRM is a set of features on the Experience Cloud platform designed to manage business relationships with a channel of partners.

✅ A. Automating partner onboarding process:
This is a primary benefit of PRM. The "lifecycle management" mentioned directly refers to the partner journey from recruitment and application to training, approval, and activation. PRM automates this with tools like automated welcome emails, task assignments, and required training checklists before granting access.

✅ C. Providing reports and dashboards access to partners:
Transparency is a key tenet of PRM. By providing partners with dedicated reports and dashboards on their performance (e.g., leads converted, opportunities influenced, marketing fund usage), DF can align incentives and help partners focus on the most productive activities.

✅ D. Preventing channel conflict:
This is solved through deal registration. This process allows a partner to formally claim credit for an opportunity they are working on. Once registered, the deal is protected for that partner, preventing other partners or the internal sales team from pursuing the same customer and causing conflict. This builds trust in the partner ecosystem.

❌ B. Helping partners manage their payments and file taxes:
Salesforce is a CRM (Customer Relationship Management) platform, not an ERP (Enterprise Resource Planning) or accounting system. While PRM can track metrics used for calculating commissions or funds (e.g., influenced revenue), it does not handle the actual processing of payments, payroll, or tax calculations and filings. These functions require integration with a dedicated financial system.

Reference:
The core capabilities of Salesforce PRM are outlined in the "Partner Management" Trailhead modules and Salesforce Help documentation, focusing on onboarding, enablement, performance management, and conflict resolution—not financial operations.