Pollard Financial Services

AI-Assisted Study Note

This page brings together public scenario links and AI-assisted research notes for study use. Start with the scenario brief, make your own attempt, and open the spoiler section only when you are ready to compare.

Scenario Snapshot

Field	Detail
Start here	Original PDF (via LBA)
Scenario source	Community scenario (Gang of Four)
Current status	Live (Community Standard)
First public date	2018-08
Primary source	Open primary source
Coverage available	Scenario brief + Video or presentation + Discussion or analysis

Why This Scenario Matters

• This entry is included because it appears in the public CTA scenario corpus and has enough public evidence to track for study use.

Only Open If You Have Attempted the Scenario

The section below contains public follow-up links, board-call material, and AI-assisted notes compiled from those public sources.

Open follow-up links, Q&A, and analysis

Follow-Up Links

• Original PDF (via LBA)
• Detailed Solution Series
• Video Review

Board Insights & Common Pitfalls

Generalized Judge Questions

• Complex Sharing: “How do you ensure a client who leaves a business-sponsored plan can no longer see negotiated funds but keeps their individual personal history?”
• Apex Sharing Scale: “You proposed Apex Managed Sharing for Fund Reports. How does your solution handle the recalculation if 1 million clients change their investment portfolio in a single day?”
• LDV Performance: “With 200 million Invested Fund records, how will your ‘Performance Report’ UI remain performant? Are you using standard reports or an off-platform LWC call?”
• Identity & Licensing: “Why choose Customer Community Plus over standard Customer Community? Is the cost justified for 20 million clients?”
• Data Skew: “How do you mitigate data skew on the Account object given the 15 million employees related to a few hundred large business accounts?”

Common Mistakes

• The File Sharing Trap: Attempting to share Fund Reports using standard Salesforce Files, which hits the 2,000-entity sharing limit when funds have 100k+ investors.
• Chatter Group Overuse: Using Chatter Groups for report sharing, which fails to handle the “point-in-time” access requirement (losing access to history when leaving a group).
• Over-licensing Internal Users: Proposing Sales Cloud for all internal staff when Lightning Platform licenses often suffice for custom investment objects.
• Role Hierarchy Explosion: Creating a unique role for every Sales Rep (800+), leading to significant performance degradation.

Strong Patterns

• Virtualization for Performance: Using an LWC to “pull” real-time performance data from an external Portfolio Management System instead of storing millions of records in Salesforce.
• External Data Archiving: Explicitly offloading historical investment data to Snowflake or Big Objects to keep “Hot” data lean while meeting 7-year regulatory retention rules.
• Metadata-Driven Report Sharing: Representing Fund Reports as a custom object shared via Apex Managed Sharing or Sharing Sets (if using CC+).

Strategic Insights

• The “Security King”: Pollard is widely regarded as the ultimate test of sharing model mastery. If you can solve Pollard’s security, you can solve almost any board scenario.
• Scale-First Thinking: Requires “Login-based” community licensing and massive data volume strategies (Skinny Tables, Custom Indexes) due to the 20M client footprint.

Additional Notes

• Core Requirements: Wealth management and financial services, complex hierarchical sharing, massive user volumes.
• Key Objects: Account (B2C Customers), Opportunity (Investments), Account Team/Opportunity Team.
• Security: Famous for its “impossible” sharing requirements that test the limits of Role Hierarchy, Sharing Rules, and Apex Sharing.
• Classification: Frequently mistaken for an official scenario due to its quality and ubiquity, but confirmed as community-created.