Galaxy Cars

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	Public scenario brief mirror
Scenario source	Official or official-adjacent scenario
Current status	Retired Official
First public date	2020 (Indexed)
Primary source	Open primary source
Coverage available	Scenario brief + Video or presentation + Public Q&A + 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

• Public scenario brief mirror
• Full mock board recording
• Analysis reference

Board Insights & Common Pitfalls

Generalized Judge Questions

• 15-Year History: “The requirement specifies retaining vehicle history for 15 years. How will a distributor view sales history from 10 years ago on their mobile device without hitting storage limits?”
• Master-Detail vs. Lookup: “Why choose a Master-Detail relationship for the Vehicle-to-Distributor link? What are the implications for record ownership and locking during bulk inventory loads?”
• Financial Resilience: “If the external accounting system is down, can the distributor still complete a car sale? How does your architecture handle this ‘disconnected’ state?”
• Global Trends Analytics: “How does the Factory Manager see a ‘Year-over-Year’ comparison of truck sales across three regions? Can standard reports handle this cross-object complexity?”
• Distributor Identity: “Walk me through the SSO flow when a distributor clicks an email link to view a car’s shipping status. Is it IdP or SP-initiated?”

Common Mistakes

• Ignoring LDV History: Trying to keep 15 years of vehicle history in standard objects, leading to immediate performance degradation and storage failure.
• Sync for Credit Checks: Proposing a real-time Request-Reply to the accounting system for credit checks, which blocks the sale if the legacy system has high latency.
• License Under-provisioning: Recommending Customer Community for distributors who need to run complex “Selling Trends” reports (necessitating CC+ or Partner).
• Weak Data Migration: Failing to explain the migration of 20 million legacy records without hitting governor limits or hitting API rate caps.

Strong Patterns

• Big Object + Async SOQL: Storing the 15-year history in Big Objects and using Async SOQL or CRM Analytics to provide trending reports to HQ.
• External Data Archiving: Offloading historical manufacturing data to an external lake (Snowflake) and surfacing it via an LWC to keep the Salesforce core lean.
• mTLS for Factory Integration: Mandating Mutual TLS (mTLS) for the sensitive connection to on-premise factory and accounting systems.

Strategic Insights

• The “Supply Chain” Test: Galaxy Cars tests the architect’s ability to manage high-value physical assets (Vehicles) across a global, multi-tier distribution network.
• Predictive Manufacturing: Success hinges on using CRM Analytics to move from “Reactive” inventory to “Predictive” factory output adjustments.

Additional Notes

• Automotive digital transformation scenario focusing on global distributor networks, vehicle allocation, and long-term history.
• Formerly an official Salesforce Board scenario.