City Scooter Share (CSS)
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.
Community-Compiled Content
All material on this page — scenario briefs, solutions, presentations, and Q&A discussions — is compiled from publicly available sources including YouTube walkthroughs, community blogs, CTA coaching sites, and mock board recordings. We have only organized and presented what was found online. The architectural approaches, product recommendations, and patterns discussed may not reflect current Salesforce products, naming conventions, or best practices. Always verify against official Salesforce documentation.
Scenario Snapshot
| Field | Detail |
|---|---|
| Start here | Scenario brief PDF |
| Scenario source | Official or official-adjacent scenario |
| Current status | Official Practice (Live) |
| First public date | 2017-04 |
| Primary source | Open primary source |
| Coverage available | Scenario brief + Video or presentation + Discussion or analysis |
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
Board Insights & Common Pitfalls
Generalized Judge Questions
- IoT Data Trap: “You have 2,000 scooters pinging GPS every 30 seconds. How will your ‘Rental History’ report perform in 3 years? Why not store pings as standard records?”
- Concurrency & Locking: “What happens if 500 riders try to unlock scooters at the exact same second during a festival? How do you prevent row locking on the Depot record?”
- Integration Resilience: “The Government License API is down during rider registration. Does the rider just stand there? Describe your fallback strategy.”
- Identity Bridge: “The scenario mentions an internal LDAP system. How does Salesforce connect to it? Explain the role of the Identity Provider (IdP) in your SAML flow.”
- Theft Detection: “How do you distinguish between a scooter being stolen and one being moved by a maintenance truck? Where does the logic reside (Salesforce vs. Middleware)?”
Common Mistakes
- GPS Object Bloat: Storing every 30-second GPS update as a standard Custom Object record. This exhausts storage limits immediately.
- Master-Detail for Rentals: Making “Rental” a detail of “Scooter” causes heavy parent-record locking during high-frequency status updates.
- Synchronous License Checks: Using a synchronous callout for driver’s license verification hangs the mobile UI if the government service is slow.
- Vague QR Security: Proposing static QR code images instead of time-bound, encrypted JWTs rendered dynamically in the mobile app.
Strong Patterns
- Big Object Archiving: Using Big Objects for the massive volume of historical GPS pings and rentals while keeping the “Latest Status” field on the live Scooter record.
- IoT Buffer Layer: Using an external layer (AWS IoT or Heroku) to filter high-frequency pings and only pushing “Actionable Events” (like incidents) to Salesforce via Platform Events.
- Asynchronous Continuation: Using the Continuation pattern for slow external pricing or license verification APIs to maintain a responsive mobile experience.
Strategic Insights
- The “High-Frequency” Test: CSS probes the architect’s ability to handle rapid-fire status updates and mobile concurrency under load.
- Standard-First Reporting: Justify when standard reports work and when CRM Analytics (formerly Tableau CRM) is mandatory for high-volume telemetry.
Additional Notes
- Foundational official practice scenario focusing on IoT, high-volume transactions, and mobile-first B2C interactions.
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.