Greens and Veg

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	Current scenario brief hub
Scenario source	Community scenario (Andrew Hart / CTA202)
Current status	Live (GoF)
First public date	2021-04
Primary source	Open primary source
Coverage available	Scenario brief + Solution + Discussion or analysis

Why This Scenario Matters

• This is the strongest public written-solution scenario found in this pass.
• It is unusually valuable because the support is not just commentary; it is a genuine solution walk-through.

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

• Current scenario brief hub
• Medium walkthrough, Part 1
• Medium walkthrough, Part 2
• Scenario list reference

Board Insights & Common Pitfalls

Generalized Judge Questions

• System Risk: “You decided to replace the ‘Evergreen’ and ‘Marketplace’ systems simultaneously. What are the risks of this ‘big bang’ approach, and how would you mitigate them?”
• LDV Performance: “With 260M+ orders projected by Year 5, how will your design ensure the Order object remains performant for daily operational reporting?”
• Integration Resilience: “What happens if the Government Permit Verification API is down for 4 hours? How does your solution prevent a bottleneck in supplier onboarding?”
• Identity Layering: “Why did you choose to keep the legacy LDAP system instead of a full migration to Okta? How are you handling provisioning for external farmers?”
• Case Sharing: “How do you handle the requirement for regional VPs to see all data in their region while restricting cross-regional data, given Case limitations with Territory Management?”

Common Mistakes

• Underestimating Order Volume: Failing to provide a concrete archival strategy for 52M+ annual orders. Keeping too much data in Salesforce instead of an EDW with virtualization is a major fail.
• Ignoring Offline Needs: Suppliers (farmers) often operate in poor connectivity areas. Forgetting Mobile Publisher with offline “Store and Forward” capabilities is a frequent miss.
• Generic Integration Patterns: Using “Real-time” for legacy supplier systems. Failing to use an ESB for protocol conversion or specifying Async patterns for long verifications is a red flag.
• Suboptimal Sharing: Using Apex Sharing for high-volume objects (Orders/Cases) instead of leveraging standard Criteria-Based Sharing or Role Hierarchy.

Strong Patterns

• Dual-Invoice Model: Creating separate “Customer Orders” (from restaurants) and “Supplier Orders” (routed to specific farms) to handle the brokerage logic.
• LDV “Hot Data” Strategy: Keeping only the “last 5 orders” per customer in Salesforce for operations, while offloading the rest to an external data lake (Snowflake/AWS).
• ESB Decoupling: Using MuleSoft to decouple Salesforce from the 200+ different external systems and protocols used by global suppliers.

Strategic Insights

• The “Fit for Purpose” Legacy: A key requirement is often to keep the existing Marketplace App because it contains complex, working geolocation logic. Replacing it introduces unnecessary risk.
• Global Compliance Gate: Ensuring the “Government Permit Verification” is a hard gate in the supplier onboarding flow before any commercial activity can occur.

Date Notes

• CTAGOF lists this scenario as Apr 2021.
• CTA202’s current public page is dated 2024-12-26.
• Pedro Tavora Santos’s two-part walkthrough was published in October 2025.

Additional Notes

• Greens & Veg is a common alias for the same scenario.