Greenhouse Recycling

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	Scenario brief PDF
Scenario source	Official or official-adjacent scenario
Current status	Official Practice (Live)
First public date	2018-11
Primary source	Open primary source
Coverage available	Scenario brief + Video or presentation + Public Q&A + Discussion or analysis

Why This Scenario Matters

• One of the richest official-sample clusters because it combines:
  • a public scenario brief
  • targeted requirement-level walkthrough material
  • public full-board attempts

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

• Scenario brief PDF
• Focused breakout
• Full mock review
• Data and integration retake
• Public mock video reference

Board Insights & Common Pitfalls

Generalized Judge Questions

• Data Modeling: “Why did you choose a Lookup relationship between Waste Profile and Location instead of Master-Detail? How do you handle a profile applicable to multiple sites?”
• LDV Scalability: “With 40 million pickup records generated annually, how will your data model remain performant? What is your granular archiving strategy for these records?”
• Integration Strategy: “How does the system route requests to the correct regional logistics system (out of the four available) when a customer schedules a pickup?”
• Document Migration: “Walk me through the end-to-end technical flow for migrating 200,000 legacy PDF documents into Salesforce Content objects.”
• Security: “You used Field-Level Security to hide financial data from specialists. If they export data via the API, can they still see it? Why not use a separate object with restricted sharing?”

Common Mistakes

• Missing Junction Objects: Failing to account for the many-to-many relationship between Locations and Waste Profiles.
• Async Pattern for Scheduling: Using Fire-and-Forget for pickup scheduling when the requirement implies an immediate confirmation number (requiring Request-Response).
• Hand-waving PDF Migration: Proposing a simple “upload” without a strategy for parsing unstructured data or linking it to the migrated records.
• License Mismatch: Choosing Customer Community when requirements like External Account Hierarchy or complex manual sharing necessitate Customer Community Plus.

Strong Patterns

• Middleware-Driven Routing: Using an ESB (MuleSoft) to abstract the four regional logistics systems and two ERPs, providing a single endpoint for Salesforce.
• Platform Events for GPS: Handling high-frequency (60-second) truck location pings via Platform Events to avoid API concurrency limits.
• OCR/Parser for Data Migration: Proposing a specific document parsing layer (e.g., Amazon Textract or DocParser) before uploading to ContentVersion.

Strategic Insights

• The “Least Privilege” Test: Greenhouse Recycling heavily tests the candidate’s ability to restrict “Financial Data” while maintaining operational visibility for specialists.
• Global vs. Local Autonomy: Requires a strong Governance model (Center of Excellence) to balance regional logistics requirements with global reporting needs.

Date Notes

• The prompt filename includes the full date 2018-11-24.
• Cloud Johann’s breakout was published 2020-06-09.
• Two CTAGOF mock reviews were published 2021-11-29.

Additional Notes

• This is one of the strongest public options for practicing document migration reasoning in a CTA context.