Skip to content

Security: Quick Reference

Domain 2 (Security) is the second highest failure domain on the CTA exam. These quick-reference pages distill the essentials. Review them in under 2 hours before a mock board.

Why Candidates Fail on Security

Failure PatternWhat the Board Sees
OWD set too openCandidate does not understand the cardinal rule: access is additive only
Role hierarchy mirrors HR org chartHierarchy should model data access, not reporting lines
No systematic OWD walkthroughCandidate guesses instead of walking object-by-object
Wrong OAuth flow selectedCandidate memorized names but cannot match flow to scenario
Page layouts used as securityFLS is the only true field-level security boundary
Implicit sharing ignoredChild record owners get Read on parent Account - security gap
No external OWD considerationPartner/customer users see each other’s data

Quick Reference Guides

GuideWhat It CoversTime
Sharing Model Quick RefOWD decision tree, sharing rule types, role hierarchy design, implicit sharing, LDV impact~40 min
Identity & SSO Quick RefSAML vs OAuth vs OIDC, all 6 OAuth flows, Connected Apps, JIT, MFA, Named Credentials~40 min
Permissions Quick RefProfiles, Permission Sets, PSGs, Muting PS, FLS, CRUD, profile retirement timeline~30 min
Portal & Experience Cloud Quick RefExternal licenses, HVCP sharing sets, guest user lockdown, portal role hierarchy, share groups~30 min
Shield & Encryption Quick RefShield components, encryption schemes, key management, what breaks, compliance mapping, Event Monitoring, FAT~30 min

The Security Checklist (Use for Every Scenario)

  1. OWD per object: who is the most restrictive user? Start Private.
  2. External OWD: are there portal/community users? Set separately.
  3. Role hierarchy: designed for data access patterns, not org chart?
  4. Sharing rules: what gaps remain after hierarchy? Criteria-based preferred.
  5. Permission model: Minimum Access Profile + Permission Set Groups?
  6. FLS: which fields does each user type need? FLS, not page layouts.
  7. Identity/SSO: existing IdP? Salesforce as SP or IdP?
  8. OAuth flows: which flow for which integration? Match to client type.
  9. MFA: where is MFA enforced? IdP or Salesforce?
  10. Encryption: regulatory requirement? Which fields? Which scheme?

Board Presentation Framework

When presenting any security decision, use this 5-step structure:

  1. Recommend — state your choice
  2. Why — tie to scenario requirements
  3. Trade-off — what you sacrifice
  4. Mitigate — how you handle the trade-off
  5. Alternative — what you rejected and why

Example script: “I recommend Private OWD for Accounts because the scenario includes partner users who should not see each other’s customer data. The trade-off is increased sharing complexity - I need three criteria-based sharing rules for internal cross-team visibility. I mitigate this by keeping the role hierarchy flat at four levels and using public groups as sharing targets. I considered Public Read Only but rejected it because partner users would see all Account names, which the scenario identifies as confidential.”

Also Know These Exist

TermWhat It Is
Restriction RulesDeclaratively restrict record access beyond sharing model (further tighten, not open)
Scoping RulesFilter which records are visible per user group (e.g., show only same-region records)
SCIMAutomated user provisioning/deprovisioning between IdP and Salesforce
External Identity LicensesAuthentication-only licenses - no community data access, just login
Login DiscoveryRoutes users to the correct IdP based on email domain at login

Deep Dive References

For full coverage, see the complete Domain 2 study materials:

For compliance frameworks (GDPR, HIPAA, SOX, PCI-DSS), see DevOps Quick Reference - Compliance Section.

Sources

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.