Acme Insurance

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	Discovery index
Scenario source	Community scenario
Current status	Live
First public date	2021-02
Primary source	Open primary source
Coverage available	Scenario brief + 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

• Discovery index
• Analysis reference

Board Insights & Common Pitfalls

Generalized Judge Questions

• Independent Agent Sharing: “How do you ensure an Independent Agent can only see the policies they sold, while an Agency Manager sees all policies in their office? Why not use Apex Sharing?”
• Legacy PAS Latency: “The legacy Policy Administration System takes 15 seconds to generate a quote PDF. How do you prevent the user’s browser from timing out?”
• Coverage Modeling: “Why choose to model ‘Coverage’ as a child object of ‘Policy’ rather than fields? How does this impact your Large Data Volume (LDV) strategy?”
• Disaster Peak Loads: “How does your architecture handle the massive spike in ‘First Notice of Loss’ (Claims) after a natural disaster? Will your integration scale?”
• Compliance Monitoring: “How are you protecting SSNs and Health Data? Can you demonstrate who accessed a specific policyholder’s record yesterday?”

Common Mistakes

• Sharing Model Over-Engineering: Jumping straight to custom Apex sharing for agents when standard Account Teams or External Account Hierarchies would scale better.
• Ignoring Person Accounts: Attempting to force a B2B model (Account + Contact) for individual policyholders when Person Accounts are the standard architectural choice for Insurance.
• Synchronous Quote Traps: Proposing real-time synchronous REST calls for quotes from slow legacy systems, which hits concurrent request limits.
• Underestimating LDV Reporting: Proposing standard Salesforce reports for 10M+ policies and claims. CRM Analytics or virtualization via Salesforce Connect is expected.

Strong Patterns

• Asynchronous Continuation: Using a “Continuation” pattern or Platform Events for slow legacy PDF generation to provide a better UI experience without timeouts.
• Headless Claims Flow: Implementing a “Headless Flow” for First Notice of Loss to handle peak loads during disasters without requiring a full portal login for every guest.
• Shield for HIPAA: Mandating Salesforce Shield (Platform Encryption and Event Monitoring) to satisfy strict insurance privacy regulations.

Strategic Insights

• The “B2C Complexity” Test: Acme Insurance tests the architect’s ability to manage high-volume personal data alongside a complex multi-tier distribution model (Captive vs. Independent agents).
• Insurance Cloud Alignment: While often presented as a core Service Cloud scenario, alignment with Financial Services Cloud (Insurance) patterns is increasingly expected.

Additional Notes

• B2C insurance carrier scenario focusing on policy management, claims (FNOL), and multi-tier agency distribution.
• Very high data volumes and strict regulatory compliance requirements.