Skip to content
theCodeFlash

Quick Reference: Communication (Domain 7)

Fast-track refresher for Domain 7. Communication is scored independently across the entire board performance. There is no separate “communication section.” Judges assess how you present, defend, and adapt throughout.

Domain 7 Objectives at a Glance

ObjectiveWhat Judges EvaluateHow It Shows Up
7.1 Articulate benefits, limitations, and design choicesEvery time you explain a decisionPresentation + Q&A
7.2 Use visualization and documentation toolsDiagram quality, readability, labelingArtifacts review
7.3 Handle unexpected roadblocksWhen judges introduce new constraintsQ&A challenges

The meta-skill

Communication is the only domain scored purely on how you deliver, not what you deliver. A technically sound solution presented poorly can fail Domain 7. A good solution presented clearly and confidently will score well.

The Three-Act Presentation Structure

Forty-five minute presentation broken into three acts: business context framing, artifact-by-artifact solution walkthrough, and a closing recap covering top decisions, trade-offs, and a seven-domain sweep.
Figure 1. The three-act structure ensures judges receive business context before technical artifacts and leave the presentation with a clear mental model. The seven-domain sweep in Act 3 is a safety net: a domain that receives zero coverage can fail a candidate regardless of strength elsewhere.

Artifact Time Budget (45-Minute Presentation)

Time rollover rule

The presentation has a fixed 45-minute allocation. Any unused presentation time automatically rolls into the 40-minute Q&A session - this is a structural rule, not an intentional buffer strategy. Plan to use the full 45 minutes.

ArtifactMinutesWhat to Cover
Opening - business context, requirements, assumptions3-5Frame the problem like a CXO briefing
System Landscape4-5All systems, roles, interactions, protocols
Data Model4-5Key objects, relationships, cardinality, LDV
Integration Architecture4-5Data flows, sync/async, error handling
Security & Identity3-4Auth, sharing model, portal security
Actors & Licenses2-3User types, license recommendations
Role Hierarchy2-3Sharing model, territory mgmt
Data Migration2-3Strategy, tools, sequencing
Governance & DevOps3-4Environments, CI/CD, release strategy
Risks & Mitigations2-3Top risks with concrete mitigations
Closing - recap, trade-offs, 7-domain sweep2-3Leave judges with a clear mental model

The “Because” Framework

WeakStrong
”I chose MuleSoft""I chose MuleSoft because the scenario has 6 external systems needing shared transformations and the client has MuleSoft expertise"
"I recommend a single org""I recommend a single org because all 3 BUs share customers, need unified reporting, and data volume is within governor limits"
"I added a CDN""To meet the 2-second page load SLA across 15 global offices, I introduced a CDN layer for static assets”

Pass vs. Fail Communication Signals

PassingFailing
Every solution tied to a requirementSolutions described without context
Proactively identifies trade-offsOnly mentions trade-offs when asked
Adapts when challenged with new infoRigidly defends everything
Concise answers, stays on timeRambles, repeats, runs out of time
Clean, labeled diagrams with legendsCluttered or unreadable diagrams
Acknowledges gaps honestlyBluffs or gives vague answers
Balances business and technical languageOnly speaks in technical jargon

The 7-Domain Sweep Technique

In your closing, address all 7 domains with one sentence each - a domain that gets zero score can fail you regardless of how strong everything else is.

“Let me confirm I’ve addressed all seven domains: For System Architecture, I recommend a single org with Sales and Service Cloud. For Security, I’ve designed an SSO flow with SAML and a role hierarchy supporting data isolation. For Data, I’ve addressed LDV with skinny tables and archival…”

The domain zero trap

Judges score each domain independently. A zero in any single domain can fail you regardless of how strong you are everywhere else. Even a brief mention in your sweep is better than silence.

Reverse-Engineered Use Cases

Use Case 1: The Defensive Q&A Failure

Situation: A candidate designed a point-to-point integration approach. A judge asked “Why not middleware?” The candidate got defensive: “Point-to-point is fine for this.”

What went wrong: No trade-off articulation, no acknowledgment of the valid alternative.

What to do instead: “I considered middleware. For this scenario with only 2 external systems and simple data flows, point-to-point reduces cost and complexity. If the client adds more systems in phase 2, I would revisit and introduce middleware at that point.”

Use Case 2: The Mid-Presentation Correction

Situation: While presenting the data model, a candidate realized they had the wrong relationship type between two objects.

What to do: Correct it openly. “On reflection, this should be a master-detail relationship, not a lookup, because we need cascade delete and roll-up summaries for the invoice line items. Let me update that.” Judges respect self-correction over stubbornly defending a mistake.

Use Case 3: The Time Management Save

Situation: A candidate spent 20 minutes on system landscape and data model, leaving only 15 minutes for 5 remaining artifacts plus closing.

What to do: Summarize remaining artifacts at a higher level (1-2 minutes each), then use the 7-domain sweep in your close. Prepare deeper detail for Q&A instead. A complete but concise presentation scores better than a half-finished detailed one.

Deep-Dive References

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.