Case Study 3: GlobalTrade Logistics - Presentation Notes
Work in Progress
This content is currently being reviewed for accuracy and will be updated soon.
Presentation Guide
This page turns the worked solution into a boardroom delivery outline. Use it after you have completed the case study and reviewed the reference solution.
Presentation Snapshot
| Field | Detail |
|---|---|
| Open after | Worked Solution |
| Format | 45-minute presentation + 45-minute Q&A |
| Study role | Rehearse structure, timing, and transitions |
| Related pages | Case Study Overview, Scenario Paper, Q&A Preparation |
Presentation Focus
Go deep on three high-risk decisions and keep six supporting artifacts at summary level.
Opening (3 min)
“GlobalTrade Logistics faces a triple challenge: consolidating three fragmented Salesforce orgs, integrating a cold-chain acquisition, and managing 413 million historical tracking events growing at 50 million per year. My solution prioritizes three decisions that determine success or failure: the LDV strategy, carrier integration consolidation, and multi-region security with data residency.”
Show System Landscape. Frame the scale: 5,800 users, 18 countries, 413M records, 40+ carrier APIs, 24-month timeline. State the single-org decision and Hyperforce choice. Briefly mention licensing model: Sales Cloud + Service Cloud + Field Service + Experience Cloud + Shield.
Deep Dive 1: LDV Tiered Storage (8 min)
“The combined tracking volume is 413 million records. The NA org already shows 8.2-second page loads with 210M - combining all orgs makes this worse.”
Three-tier model: hot (90 days, ~12M records, standard objects, sub-3s queries), warm (90 days-2 years, Big Objects with brokered Apex read access, standard SOQL on indexed fields), cold (2-5 years, ~300M records in AWS S3 + Athena data lake, federated to Salesforce via Salesforce Connect and CRM Analytics External Data connectors). Data 360 is reserved for real-time profile unification and segmentation, not cold archival — the Salesforce CRM connector in Data 360 does not ingest Big Objects and Data 360’s credit-based pricing is an order of magnitude more expensive than S3 + Athena for pure archival workloads. Nightly Apex batch ages hot to warm. One-time historical backfill of 210M events uses Bulk API 2.0 against the Big Object, not Apex batch DML. Shipment detail page: hot events load immediately; “Load Full History” button paginates up to 200 rows synchronously per Big Object SOQL call and uses async Platform Events for larger result sets. Trade-off: operational complexity of three storage tiers, but the alternative is an unusable org.
Cover reporting: CRM Analytics runs its dataflow every 4 hours (not 6 hours) to meet Req 34’s 4-hour refresh SLA. Hot-tier data feeds the global operations dashboard; S3 + Athena via CRM Analytics External Data connectors handles 5-year historical trend analytics without impacting transactional performance. Cross-region executive dashboard consolidates KPIs with drill-down by region. Cold-chain compliance reporting queries temperature logs for FDA/MHRA/TGA audit evidence.
Deep Dive 2: Carrier API Canonical Model (8 min)
“Currently 40+ point-to-point integrations across three orgs. When a carrier makes a breaking change, it takes weeks to diagnose which org is affected.”
MuleSoft API-led connectivity with a Canonical Shipment Event schema. Each carrier gets a thin system API translating native format. New carrier = one system API, zero changes to Salesforce. Top 10 carriers (80% volume) migrate in Phase 1; remaining 30 over 12 months. FrostGuard follows the same pattern: MQTT-to-MuleSoft bridge aggregates 60-second readings into 5-minute summaries; excursion alerts bypass aggregation for 2-minute SLA.
Walk through error handling briefly: Anypoint MQ for async buffering, dead-letter queues per integration, circuit breaker on synchronous customs screening. Proactive exception management: late shipments, routing deviations, customs holds, and temperature excursions all auto-detect and create cases with configurable SLAs.
Deep Dive 3: Multi-Region Security (7 min)
“Single global org creates tension between unified visibility and regional isolation.”
Account Private OWD + Enterprise Territory Management with one active Territory Model containing three regional parent territories (NA, EU, APAC) and 18 country leaf territories nested underneath — Salesforce allows only one active Territory Model per org at a time, so “3 regional models” is not the right framing. The cold-chain branch is a parallel role hierarchy under the COO. German rep sees only German accounts by default. 4,200 global accounts get criteria-based sharing scoped to a Global_Account_Regions__c field so the rule only grants access to the regions actually touching the account, not to every user in every regional branch.
Shipment has two Account lookups — Shipper_Account__c and Consignee_Account__c — so a cross-border shipment from a German shipper to a Japanese consignee is visible to both the NA/EU Shipper rep and the APAC Consignee rep through their respective account relationships. Shipment OWD is Private (not Controlled by Parent) to avoid parent-child data skew at the 26M-row scale; sharing is implemented via criteria-based sharing on the Shipper territory plus Apex Managed Sharing for the Consignee. Enterprise Territory Management can only be applied to Account, Opportunity, Case, and Lead, so Shipment itself is not in a Territory Model — its sharing is rule-based.
Japan residency is committed, not punted: Decision 1’s decision tree says if Legal’s APPI and FISC review concludes contractual safeguards are sufficient, Japan data stays in Hyperforce EU Frankfurt with BYOK tenant keys stored in Japan; if physical residency is required, the pre-budgeted Hyperforce Japan split-org provisions in month 10 with MuleSoft bridging cross-border shipments at +$420K/year license + $180K integration. Shield Platform Encryption protects confidentiality, not residency.
Sensitive data (hazmat, denied-party hits, pharma cold-chain): Restriction Rules correctly described. The rule FILTERS OUT matching Shipments from users who do NOT hold the Sensitive_Shipment_Data_Access custom permission. Users with the permission set see sensitive shipments normally; users without it have those records hidden from list views, reports, and API. Restriction Rules subtract access; they do not grant it. Audit trail via Shield Event Monitoring with jurisdiction-specific retention periods.
Portal data isolation: Customer Community Plus licenses. Sharing Sets grant each portal user access to Shipments where the Shipment’s Shipper_Account__c or Consignee_Account__c matches the portal user’s own Account. Sharing Sets key off the user’s Account or Contact directly — they do not rely on the AccountContactRelation junction. Three portal roles per account (admin, operations, finance) are implemented via permission sets. Account Role Optimization is enabled to handle the 35K-account scale without the UserRole table growing to 105K rows and causing sharing recalc latency.
Supporting Artifacts (10 min)
Identity (1 min): Entra ID SAML 2.0 + SCIM for 5,800 employees. Portal: Salesforce Identity + MFA; enterprise clients federate via SAML. FrostLine: JIT provisioning via Entra. Session timeouts: 8 hours office, 4 hours mobile/field.
Mobile and Field Operations (2 min): Field Service is chosen for the native service data model (Service Territories, Service Resources, Work Types, Work Orders, Service Appointments), not because it is the only offline path — the standard Salesforce mobile app also supports offline via Briefcase Builder. 800 warehouse workers on company-managed iPads use the Field Service Mobile App with Briefcase Builder priming for facility-level work orders. 200 drivers on BYOD use Field Service Mobile App with native offline priming of the day’s assigned Work Orders and Service Appointments. Intune MDM provides container-level data protection for BYOD. Proof of delivery via photo + digital signature. Conflict resolution: last-write-wins for status fields, append-only for photos/signatures. Supervisors get real-time visibility dashboards.
Document Management (1.5 min): 6M documents/year. Salesforce Files for active documents (last 12 months). Older documents archived to S3 via MuleSoft with metadata reference in Salesforce. Portal users upload via shipment record with virus scan and file type validation. “Download Document Bundle” generates ZIP per shipment. Trade compliance bundles grouped per jurisdiction. 7-year retention for regulatory documents.
Data Migration (1.5 min): Three-phase: Phase 1 consolidates accounts and migrates NA. Phase 2 handles EU (MuleSoft abstracts SAP upgrade) and commits the Japan residency decision (stay on Hyperforce EU with BYOK OR split to Hyperforce Japan per Legal’s APPI finding). Phase 3 migrates FrostLine. Account dedup: Informatica matching (Company Name + Tax ID), manual review for top 200 by revenue. 210M historical tracking events load to Big Objects via Bulk API 2.0, not Apex batch DML. Zero-downtime portal cutover: DNS flip at CDN edge after reconciliation sweep, MuleSoft Anypoint MQ absorbs the 60-minute write freeze, total customer-facing downtime is a sub-2-minute DNS propagation. Rollback: source org stays as system of record during parallel run.
Governance (1 min): GARB for cross-region changes. Regional admin teams for local config within guardrails. All automation via Flow or Apex (no Process Builders). All integrations through MuleSoft.
Environment (1 min): Full Copy for performance testing at 413M-record scale (Unlimited Edition ships with 1 Full Copy). Three regional Partial Copy for independent UAT (NA, EU, APAC) — Unlimited Edition ships with 1 Partial Copy, so 2 additional Partial Copy add-ons are purchased and budgeted under Phase 1 licensing. EU sandbox tests GDPR automation. Dev sandboxes per workstream.
Roadmap (1 min): 24-month program with phase overlap. Foundation + NA by month 8. EU starts month 6 (data extraction during NA parallel run). Cold-chain month 12. EU SAP swap month 16-18 insulated by MuleSoft. Carrier consolidation top-10-first over 12 months.
Transitions
- Opening to LDV: “Let me start with the highest-risk technical decision - handling 413 million tracking events.”
- LDV to Carriers: “The tracking data feeds in through 40+ carrier integrations. Let me show the consolidation approach.”
- Carriers to Security: “Now that data flows from everywhere, the question is: who sees what, in 18 countries with different laws?”
- Security to Supporting: “With the three highest-risk decisions covered, let me walk through the remaining artifacts.”
- Supporting to Close: “Before I wrap up, the three biggest risks and how my architecture mitigates them.”
Closing (3 min)
Three risks and mitigation:
- LDV performance: Tiered storage, daily CRM Analytics monitoring, trigger at 15M hot-tier records
- EU dual transformation (SF + SAP): MuleSoft abstraction; EU SF cutover month 10, SAP swap month 16 - never simultaneous
- Portal at 8K concurrent: CDN caching of static assets, LWC lazy loading, native LWC wire adapters against the Shipment hot tier that already lives in Salesforce (no MuleSoft cache round-trip for data the org already owns), 2-month load test phase with k6 simulation
“This is a consolidation where architecture must balance global unity with regional autonomy, handle extreme data volumes, and sustain 40+ integration points - without disrupting 35,000 clients tracking shipments in real-time.”
Timing Checkpoints
| Segment | Duration | Cumulative |
|---|---|---|
| Opening | 3 min | 3 min |
| LDV Deep Dive | 8 min | 11 min |
| Carrier Deep Dive | 8 min | 19 min |
| Security Deep Dive | 7 min | 26 min |
| Supporting Artifacts | 10 min | 36 min |
| Closing | 3 min | 39 min |
| Risk & Trade-offs | 3 min | 42 min |
| Buffer | 3 min | 45 min |
Related Topics
Always verify against official Salesforce documentation
This content is study material for CTA exam preparation. Content compiled and presented with AI assistance. Not affiliated with Salesforce.
Personal study notes for the Salesforce CTA exam. Content compiled from VJ's study notes, official Salesforce documentation, community sources, and online publicly available content, then organized and presented with AI assistance. Not affiliated with Salesforce. © 2025–2026 VJ Srivastava.