Patient Travel Support Foundation (PTSF)
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
Section titled “Scenario Snapshot”| Field | Detail |
|---|---|
| Start here | Discovery index |
| Scenario source | Official or official-adjacent scenario (Scenario 602 / Step 1 Evaluation) |
| Current status | Official Practice (Live) |
| First public date | 2021 |
| Primary source | Open primary source |
| Coverage available | Scenario brief + Video or presentation + Discussion or analysis |
Only Open If You Have Attempted the Scenario
Section titled “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
Section titled “Follow-Up Links”Board Insights & Common Pitfalls
Section titled “Board Insights & Common Pitfalls”Generalized Judge Questions
Section titled “Generalized Judge Questions”- Sensitive Data Access: “How do you ensure a Volunteer can only see the patients they are currently assisting? Why choose a Private model over hierarchies?”
- Integration Reliability: “What happens if the Travel Agency API is down when a booking is submitted? Describe your error handling and retry mechanism.”
- Privacy Compliance: “How are you handling the ‘Right to be Forgotten’ for patients? Can you mask records while preserving financial audit trails?”
- Encryption Impact: “You recommended Platform Encryption. How does this affect the staff’s ability to search for patients by name or medical ID?”
- Org Strategy: “Why choose a Single-Org strategy for a global foundation? How do you partition data without a multi-org overhead?”
Common Mistakes
Section titled “Common Mistakes”- Public Patient Data: Using a “Public Read/Write” model for Patient records is a critical HIPAA/GDPR failure for medical data.
- Synchronous Booking: Using synchronous Request-Response for flight bookings. Travel APIs are notoriously slow; use Asynchronous patterns (Platform Events/Queueable) to avoid UI timeouts.
- Data Skew Traps: Linking all travel requests to a single “Foundation” Account creates a large parent-child skew that blocks record locking.
- Master-Detail Overuse: Using Master-Detail for everything and hitting the 2-master limit or blocking independent record ownership for volunteers.
Strong Patterns
Section titled “Strong Patterns”- The “Golden Path” focus: In this short mock, successful candidates focus strictly on Intake -> Approval -> Booking -> Feedback without over-engineering.
- Shield for Compliance: Using Shield (specifically Deterministic Encryption) to balance security needs with the requirement to search for patients.
- Experience Cloud (formerly Community Cloud) for Volunteers: Using Customer Community Plus to allow volunteers to manage travel requests while maintaining strict security boundaries.
Strategic Insights
Section titled “Strategic Insights”- 60-Minute Discipline: Success in this “Step 1” scenario depends on making decisive, standard-first choices quickly rather than exploring multiple custom alternatives.
- NGO Licensing: Be prepared to justify the use of Nonprofit Cloud features vs. standard Service Cloud objects.
Additional Notes
Section titled “Additional Notes”- A “short mock” designed to test fundamental architect skills: medical compliance, high-volume data, and multi-region logistics.
- Often used as the benchmark for the Step 1 Architect Evaluation.
Related Study Topics
Section titled “Related Study 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.