Salesforce ArchitectureArchitect (Hardest)experience-cloudportalsstrategy
Architect Experience Cloud strategy for B2B and B2C portals
Real World Scenario
Company needs partner portal, customer self-service, and employee community with different branding and data isolation.
Expected Answer
• Separate sites or shared site with audience-specific pages based on isolation needs
• LWR vs Aura template choice for performance and SEO requirements
• Sharing sets, sharing rules, and account-based visibility for partner isolation
• Identity: SSO for partners, social login for consumers where appropriate
• Headless API layer for mobile app same backend as Experience site
• Governance: who can publish content and expose new objects to community
• License model: Customer Community Plus vs Partner Community cost planning
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Stay within limits by: Separate sites or shared site with audience-specific pages based on isolation needs. Bulkify everything — never query or DML in loops. Sharing sets, sharing rules, and account-based visibility for partner isolation. Experience Cloud multi-site architecture must be decided early—retrofit isolation is painful. Document the decision in an ADR and align with enterprise standards.
Architect Perspective
Experience Cloud multi-site architecture must be decided early—retrofit isolation is painful.