Universal Racing (Flower Racing)

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 (Ladies Be Architects)
Current status	Live
First public date	2020-09
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

• Discovery index
• Video reference (Flower Racing)
• Solution summary

Board Insights & Common Pitfalls

Generalized Judge Questions

• Person Accounts Strategy: “Why did you choose Person Accounts for Racers? What are the trade-offs regarding storage impact and integration with legacy B2C systems?”
• LDV Pledges: “How are you handling the 10M+ Pledge records? What is your granular archival strategy, and why choose Big Objects over an external Data Lake?”
• Mobile Authentication: “Which OAuth flow did you choose for the Racer Mobile App? Why is the Authorization Code Flow with PKCE preferred over the User-Agent Flow here?”
• Real-time Validation: “How do you handle the IARA (International Amateur Racing Association) ID validation? What happens if the service is down during racer registration?”
• Charity Visibility: “How do external Charities see only their own Pledges? Describe the choice between Sharing Sets and CC+ role-based sharing.”

Common Mistakes

• Charity License Mismatch: Choosing standard Customer Community for Charities when they need to run complex reports or see non-owned records (necessitating CC+ or Partner licenses).
• Ignoring External IDs: Failing to map the unique IARA ID as an External ID in Salesforce, leading to data migration and upsert failures.
• PCI Compliance Risk: Attempting to store credit card data directly in Salesforce instead of using a tokenization/iframe approach with a payment gateway.
• Poor Migration Sequencing: Forgetting that Charities (Accounts) and Races must be loaded before Registrations and Pledges to maintain referential integrity.

Strong Patterns

• Standard-First Analytics: Using CRM Analytics (Tableau CRM) for ad-hoc analysis on 5 years of historical data to avoid standard report performance failures.
• Mobile Publisher: Leveraging Salesforce Mobile Publisher for Communities to provide a branded experience while keeping the development footprint declarative.
• ESB Orchestration: Using middleware to handle the complex handshake between the IARA validation service and the Racer portal.

Strategic Insights

• The “Self-Correction” Test: Judges value candidates who can acknowledge a row-locking or OWD error during Q&A and immediately propose a fix (e.g., shifting to Public Read-Only).
• Global Racer Portals: Success hinges on balancing the B2C Racer experience with the B2B Charity/Sponsor requirements.

Additional Notes

• Alias: Frequently referred to as “Flower Racing” in LBA materials.
• Focuses on racer registration, charitable pledges, and international event logistics.