Case Study 05: ScreenVault Studios — Q&A Preparation
AI-Generated Content — Use for Reference Only
This content is AI-generated and has only been validated by AI review processes. It has NOT been reviewed or validated by certified Salesforce CTAs or human subject matter experts. Do not rely on this content as authoritative or completely accurate. Use it solely as a reference point for your own study and preparation. Always verify architectural recommendations against official Salesforce documentation.
Q&A Format
Duration: 30 minutes following 30-minute presentation Strategy: State your position, give the reasoning, acknowledge the trade-off. Keep answers to 1-2 minutes.
Data Architecture
Q1: How does the rights conflict detection handle edge cases like partially overlapping windows or non-exclusive rights?
The Apex trigger queries existing active Content Right records matching the same Content Title and Territory with overlapping date ranges. For exclusive rights, any overlap is blocked. Non-exclusive rights do not conflict with each other — the trigger only fires when the proposed or existing right has Exclusivity = Exclusive. Partial window overlaps are caught by the date range comparison: existing.WindowStart < proposed.WindowEnd AND existing.WindowEnd > proposed.WindowStart.
Q2: 12,000 licensing contracts — what happens to performance when a rep searches available content across 50 territories?
The availability search queries Content Right records filtered by territory and date range, which is a well-indexed SOQL query. 12,000 contracts across 1,800 titles and ~50 territories means roughly 6-7 rights per title on average. Custom index on Content Title + Territory + Window End keeps query times under 1 second. If this scales significantly, a pre-computed availability cache (scheduled Apex recalculating nightly) replaces the real-time query.
Q3: Why custom objects for rights instead of Salesforce CPQ or Vlocity/Industries CPQ?
CPQ is designed for product configuration and pricing in a quote-to-cash flow. Content rights are fundamentally different — they are constraints on who can exploit intellectual property in specific geographies and time windows, not product line items. CPQ lacks native territory-window-exclusivity conflict detection. Building on CPQ would mean fighting the data model rather than extending it. Custom objects with purpose-built validation are simpler and more maintainable.
Q4: How do you handle a title that is in production but already has pre-sold licensing rights?
Content Title has a Status picklist (Development, Production, Post-Production, Released). Content Rights can be created against titles in any status — pre-sales are standard practice in media. The Production object links to the same Content Title, so licensing reps can see production status alongside active rights. A report shows titles with pre-sold rights and their production timelines, flagging any where production is behind schedule relative to rights window start dates.
Integration
Q5: You chose MuleSoft Composer over Anypoint. What if integration needs grow?
At 60K events/day across 8 systems, full Anypoint is over-provisioned. Composer handles the SAP, CMS, and Rights DB integrations at this volume. The highest-volume path (Snowflake at 50M events/day) uses Data Cloud’s native connector, not middleware at all. If SVS acquires another company or integration volume doubles, Composer can be upgraded to Anypoint — the integration patterns (API-led, event-driven) remain the same. The decision is right-sized for now without closing future doors.
Q6: Data Cloud zero-copy to Snowflake — what are the limitations?
Zero-copy provides read access, not write-back. Salesforce cannot push data into Snowflake this way. Latency depends on Snowflake query performance — complex aggregations may take seconds, not milliseconds. Calculated insights refresh on a schedule (hourly or daily), not real-time. For churn scoring, hourly refresh is sufficient. The trade-off is acceptable: we avoid ETL infrastructure entirely, and the scores are fresh enough for marketing and service use cases.
Q7: How do you handle the Rights DB transition if the developer leaves before month 6?
The integration layer is the insurance policy. By month 3, the bidirectional sync is operational and Salesforce has a complete copy of all rights data. If the developer leaves, we accelerate the cutover — Salesforce becomes source of truth earlier, and the Rights DB runs read-only without developer maintenance. The 6-month timeline has 3 months of buffer built in. Knowledge transfer documentation happens in months 1-2 as part of the integration build.
Q8: Subscriber webhooks from the streaming platform — how do you handle spikes like a viral show launch?
Platform Events provide the ingestion layer with built-in queuing. Salesforce can handle 250K Platform Events per hour (standard high-volume limit). At 5,000 subscriber events per day on average, even a 10x spike (50K) is well within limits. Flow automation processes events asynchronously. If a truly extreme event occurs, the streaming platform’s webhook retry mechanism handles temporary back-pressure.
Security & Sharing
Q9: Content Title is Public Read Only — does that expose sensitive information?
No. Content Title holds catalog metadata: title name, genre, cast, production status. All financial data lives on Content Right (Controlled by Parent, inherits Private from Account) and Opportunity (Private OWD). A marketing specialist can see that a documentary exists and its genre, but cannot see what Netflix pays for it. Field-Level Security on Content Right’s LicenseFee and payment term fields provides a second layer restricted to Licensing and Finance profiles.
Q10: How do you prevent a licensing rep from seeing subscriber data, and vice versa?
Role hierarchy separation. Licensing and Consumer teams are in different branches with no cross-branch visibility. Account OWD is Private, so a licensing rep owns Licensing Partner accounts and sees nothing about Subscriber accounts. The consumer team owns Subscriber accounts and cannot see licensing deals. Content Title (Public Read Only) is the only shared data — intentionally, because both teams need catalog awareness. No sharing rules cross the boundary.
Q11: GDPR for the London office — how do you handle subscriber data deletion requests?
Subscriber records flagged with DataResidencyRegion = EMEA are subject to GDPR. Right-to-erasure requests trigger a Flow that anonymizes PII fields on the Account and related records (Subscription, Cases). Marketing Cloud suppression lists prevent re-contact. Data Cloud retains anonymized engagement data for aggregate analytics but removes PII linkage. The process is auditable via Field Audit Trail showing what was anonymized and when.
Marketing
Q12: Marketing Cloud live at month 5 with basic segmentation — won’t that hurt subscriber retention compared to Mailchimp?
Month 5 Marketing Cloud delivers the same campaign types Mailchimp runs today: welcome series, re-engagement, winback. The segmentation is initially demographic (subscription tier, signup date, region) — same as current Mailchimp. No regression. Once Data Cloud connects at month 7, behavioral segments (viewing patterns, churn scores) upgrade targeting significantly. The trade-off is 2 months of equivalent-to-Mailchimp performance before the uplift arrives.
Q13: B2B and B2C in the same Marketing Cloud instance — how do you prevent cross-contamination?
Separate Business Units within Marketing Cloud. B2B Business Unit manages partner communications (content announcements, licensing promotions). B2C Business Unit manages subscriber journeys. Each has independent sender profiles, suppression lists, and consent tracking. Data extensions are scoped to business units. A partner contact never receives a subscriber winback email, and a subscriber never receives a licensing announcement.
Mobile & Production
Q14: Offline sync for 200 crew members — what technology specifically?
Salesforce Mobile App with Briefcase Builder. Briefcases define which records sync offline per user — their assigned Production, related Crew Assignments, Contact records for talent and vendors, and Content Files for permits and schedules. Data primes when on Wi-Fi. Offline edits (equipment check-in, schedule updates) sync when connectivity returns with conflict resolution favoring the latest timestamp. Rejected Field Service mobile because there is no dispatch or work order workflow — Briefcase is lighter and sufficient.
Q15: BYOD for production crews creates security risk. How do you mitigate?
Three layers. First, MDM (Mobile Device Management) enrollment is required before Salesforce Mobile App installation — enforces screen lock, OS version minimums, and enables remote wipe. Second, the Salesforce Connected App restricts access to managed devices only via device-based connected app policies. Third, Briefcase limits offline data to production-specific records — a crew member’s device never contains licensing deal terms or subscriber PII. If a device is lost, MDM remote wipe removes the Salesforce container without affecting personal data.
Question Categorization
| Domain | Questions |
|---|---|
| D1 System Architecture | Covered in presentation deep dives |
| D2 Security | Q9, Q10, Q11, Q15 |
| D3 Data | Q1, Q2, Q3, Q4 |
| D4 Solution Architecture | Q12, Q13 |
| D5 Integration | Q5, Q6, Q7, Q8 |
| D6 Dev Lifecycle | Covered in governance artifact |
| D7 Communication | Q14 |
Q&A Survival Rules
- Answer the question asked — do not pivot to a topic you prepared better for
- State position first, then reasoning: “I chose X because Y. I rejected Z because W.”
- Name the trade-off proactively — judges respect honesty over pretending there is no cost
- Say “I don’t know” when appropriate: “I would validate that during the design phase”
- Stay within 1-2 minutes per answer