Case Study 5: ScreenVault Studios - 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 two high-risk decisions, address one constraint-driven decision, and keep the other artifacts at summary level.
Opening (3 min)
“ScreenVault Studios operates three distinct business lines (B2B content licensing, D2C streaming, and content production) that share a content library but have very different operational needs. The architecture must serve all three on a single platform while addressing two critical risks: replacing a fragile rights management system maintained by a single developer, and connecting 50 million daily streaming events to drive subscriber retention. My solution centers on a custom content rights model with conflict detection, Data 360 (formerly Data Cloud) for Snowflake integration, and an accelerated Marketing Cloud rollout to meet a hard Mailchimp deadline.”
Show System Landscape. Frame the scale: 1,200 employees, 500 licensing partners, 2M subscribers, 1,800 content titles, 14-month timeline.
Deep Dive 1: Content Rights Data Model (10 min)
“The licensing business is built on rights - who can show what content, where, when, and exclusively. A single title can have dozens of active rights across different territories and windows. The worst thing that can happen is selling conflicting exclusive rights.”
Walk through the Content Right object: junction between Content Title and Account. Each record captures territory, window dates, platform type, exclusivity, and pricing. Apex before-trigger validates on every insert/update - queries active exclusive rights for same title + territory + overlapping date range. If conflict found, block the save.
Why not Opportunity Products: Products lack multi-dimensional constraint logic. Each Content Right needs independent validation against the global rights picture, not just within one deal.
Rights availability search: reps query available content by territory and window via indexed SOQL.
Transition from Rights DB: Months 1-3 Salesforce reads from Rights DB while building a complete copy via CDC and bulk load. Month 3 dual-write begins, satisfying the scenario’s required 30-day parallel operation with daily discrepancy reporting. Month 4 Salesforce takes over as source of truth on zero-discrepancy exit. The Rights DB runs read-only through month 9 as a reconciliation safety net, then decommissions. This eliminates the single-developer risk because the Rights DB interface no longer receives write traffic after month 4.
Deep Dive 2: Snowflake + Data 360 (8 min)
“50 million streaming events per day cannot come into Salesforce. But subscriber churn prediction and content ROI analysis require that viewing data. Data 360 solves this with zero-copy - no data movement, no ETL maintenance.”
Data 360 maps Snowflake tables directly. Calculated insights produce subscriber-level churn scores and engagement segments that flow into Salesforce as actionable data. A declining engagement score triggers a re-engagement journey in Marketing Cloud or surfaces the subscriber in a service agent’s at-risk queue.
Content performance: Data 360 aggregates viewing metrics per title. Licensing reps see which content performs well on streaming, informing their pitch to licensing partners.
The rejected alternative, a nightly ETL batch of aggregated data into custom objects, would be stale (24-hour lag), brittle (schema changes break ETL), and unable to support real-time segmentation.
Constraint Decision: Marketing Cloud Timing (5 min)
“Mailchimp expires in 5 months. This is the hardest constraint in the program - Marketing Cloud must be operational for B2C subscriber campaigns before the full subscriber platform is built.”
Accelerated delivery: Marketing Cloud provisioned month 4, B2C journeys live month 5 on subscriber records via Marketing Cloud Connect. Data 360 connects month 7, upgrading to behavioral segmentation. B2B partner journeys follow.
Risk: early campaigns less targeted without Data 360. Acceptable - generic campaigns beat no campaigns.
Supporting Artifacts (10 min)
Sharing Model (1.5 min): Three role hierarchy branches isolate licensing, consumer, and production. Content Title is Public Read Only (everyone needs catalog access). Content Right inherits from Account (Private) - licensing deal terms invisible to other teams. Field-Level Security restricts pricing fields to Licensing and Finance.
Identity (1 min): Corporate SAML SSO for 1,200 employees. Partner portal with self-registration and MFA. Subscriber identity managed by streaming platform - Salesforce holds records, not logins. BYOD mobile with MDM policies.
Integration (1.5 min): MuleSoft Anypoint Platform as the integration layer. Justified over Composer by the need for CDC-triggered bidirectional sync with the Rights DB, Anypoint MQ dead letter queues for failed financial postings, and HMAC webhook verification. Data 360 handles the highest-volume path (Snowflake zero-copy). Webhooks for real-time subscriber and payment events.
Migration (1.5 min): Phase 1 loads 12,000 contracts and 1,800 titles with rights conflict validation against all imported data before go-live. Phase 2 loads 2M subscriber records via Bulk API. Each phase has a 2% error threshold; exceeding it halts migration and reverts to source system. 30-day parallel operation for the Rights DB with daily discrepancy reporting.
Governance (1 min): Monthly steering committee, bi-weekly technical review. CoE established by month 3. Rights conflict logic in Apex only for testability and query performance. SI partner transitions to managed services retainer post-program.
Environments + Roadmap (1.5 min): Full Copy sandbox for 2M-record testing. Two developer sandboxes for parallel workstreams. 14-month phased delivery: licensing first (highest risk), subscriber and marketing second (Mailchimp deadline), production and analytics third (lowest risk, absorbs schedule pressure).
Transitions
- Opening to Rights Model: “Let me start with the defining domain challenge - how to model content rights without selling conflicting licenses.”
- Rights to Data 360: “Once we have the licensing platform, the question is how to make 50 million daily streaming events actionable for subscriber retention.”
- Data 360 to Marketing: “Data 360 feeds subscriber intelligence, but we face a hard constraint - Mailchimp expires before the full subscriber platform is ready.”
- Marketing to Supporting: “With the three key decisions covered, let me walk through the remaining artifacts.”
Risk & Trade-offs (3 min)
- Rights DB developer attrition: Salesforce reaches a complete copy of all rights data by month 3, then the scenario’s required 30-day parallel operation window runs from month 3 to month 4 with daily discrepancy reporting. Salesforce takes over as source of truth immediately on zero-discrepancy exit. The Rights DB is retained as a read-only archive through month 9 to cover any trailing reconciliation before full decommission. Knowledge transfer during months 1-2 captures integration API documentation, PostgreSQL schema snapshots, and data model mapping while the developer is still engaged, so the SI partner can maintain the Rights DB interface if the developer leaves before month 3.
- Mailchimp deadline: Marketing Cloud accelerated to month 5. B2C journeys go live before full Data 360 integration. Trade-off: the first two months of Marketing Cloud campaigns use demographic segmentation only (subscription tier, signup date, region), matching current Mailchimp capability. Behavioral segmentation arrives when Data 360 connects at month 7. Acceptable because generic campaigns beat no campaigns. Automations and Content Builder assets cannot be migrated automatically from Mailchimp - they are rebuilt manually in Journey Builder and Content Builder before cutover, and the Marketing Cloud deadline assumes that rebuild work starts in month 2 alongside provisioning.
- Snowflake volume: Data 360 zero-copy eliminates data movement entirely. No ETL maintenance, no storage overhead, no schema-change breakage. Trade-off: calculated insights refresh hourly, not real-time. For churn scoring and engagement segmentation, hourly is sufficient.
- MuleSoft Anypoint licensing cost: Anypoint Platform adds licensing cost compared to Composer or native integrations alone. Justified by the need for CDC-triggered bidirectional sync, dead letter queues for financial postings, and HMAC webhook verification. These capabilities are non-negotiable for the error handling SLAs the business requires.
- Single org for three business lines: Risk of complexity growth. Mitigated by strict role hierarchy branch separation, object-level OWD isolation, and a CoE with defined change approval authority. If the business acquires another company or adds a fourth business line, the single-org decision should be re-evaluated.
Closing (3 min)
“The single-org approach with Data 360, custom rights modeling, and phased delivery gives ScreenVault a unified view across three business lines without over-engineering. The architecture right-sizes each component: Anypoint for integration orchestration where complexity demands it, Data 360 for the Snowflake connection where volume demands it, and Briefcase Builder for mobile where simplicity demands it.”
Timing Checkpoints
| Segment | Duration | Cumulative |
|---|---|---|
| Opening | 3 min | 3 min |
| Rights Data Model Deep Dive | 10 min | 13 min |
| Snowflake + Data 360 Deep Dive | 8 min | 21 min |
| Marketing Cloud Timing | 5 min | 26 min |
| Supporting Artifacts | 10 min | 36 min |
| Risk & Trade-offs | 3 min | 39 min |
| Closing | 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.