Updated for Winter '26
Salesforce Heroku Architect Exam Tips (Winter '26): How to Pass
The Heroku Architect exam tests your ability to design Heroku applications and their integration with Salesforce. These tips focus on Heroku platform services, Heroku Connect, and the architectural decision-making that defines this exam.
Written and reviewed by Krishna Mohan — ADM-201, PD1, PD2, App Builder & Consultant certified. Updated for Winter '26. Methodology · Contact
Exam At a Glance
60
Questions
105 min
Time Limit
65%
Passing Score
$200
Exam Fee
Quick Answer: What Heroku Architect Tests
- Heroku platform architecture — Dyno types (web, worker, one-off), process model, add-ons ecosystem (Heroku Postgres, Redis, Kafka), buildpacks, Pipelines for CI/CD, review apps, and Private Spaces for network-isolated deployments.
- Salesforce integration patterns — Heroku Connect for bidirectional data sync with Salesforce, direct Salesforce REST/SOAP API calls from Heroku apps, Platform Events for event-driven integration, and External Objects via Salesforce Connect pointing to Heroku Postgres.
- Security and scalability — Heroku Private Spaces for compliance (PCI, HIPAA), Shield Postgres for encryption at rest, configuring SSL/TLS for Heroku apps, horizontal scaling (dyno formation), and database connection pooling for high-throughput applications.
Highest-Weight Exam Sections
Architecture + Integration + Security = 77%. The Heroku Connect data sync pattern and Private Spaces security model are the most exam-critical topics.
Scenario Strategy: How to Approach Heroku Architect Questions
Questions describe an application or integration requirement and ask which Heroku architecture decision, integration pattern, or platform feature is appropriate. Always consider the requirement dimensions: real-time vs. batch, compliance requirements, and data volume.
- For integration pattern questions: Heroku Connect = near-real-time bidirectional sync of Salesforce data to Postgres (best for data that Heroku apps read and write back to Salesforce). Direct API = synchronous Salesforce API calls for real-time reads/writes. Platform Events = event-driven async integration. External Objects = read Heroku Postgres data from Salesforce without syncing it.
- For compliance questions: Heroku Private Spaces provide network isolation (no public internet exposure), a dedicated runtime environment, and compliance features for PCI DSS and HIPAA. Heroku Shield adds additional encryption and logging. When a scenario mentions regulated data (payment cards, health data), Private Spaces + Shield is the answer.
- For scaling questions: horizontal scaling = add more dynos (handles more concurrent requests). Vertical scaling = increase dyno size (handles larger memory workloads). Worker dynos process background jobs — scale them separately from web dynos. Connection pooling (PgBouncer) is required when many dynos need database connections simultaneously.
Mock-Test Benchmark Before Booking
75%+ on 3 timed full mocks before booking
Heroku Architect is a specialist certification primarily taken by Salesforce technical architects who need to design Heroku-based solutions. Real Heroku deployment experience — building and deploying an application, configuring Heroku Connect, and managing a Private Spaces environment — is strongly recommended before booking.
3 Concepts That Fail Most Heroku Architect Candidates
These are not the hardest topics — they are the ones where candidates are most confidently wrong. Learn the distinction early.
1. Heroku Connect — Bidirectional Sync Has Write Conflict Rules
Heroku Connect synchronises data between a Heroku Postgres database and Salesforce objects. By default it is unidirectional (Salesforce to Postgres). Enabling bidirectional sync introduces write conflicts when both sides update the same record. Candidates assume bidirectional sync just works — the exam expects knowledge of the "Salesforce wins" vs "database wins" conflict resolution setting and when each applies.
2. Dyno Types — Web vs Worker vs One-Off
Web dynos handle HTTP requests and must respond within 30 seconds (otherwise Heroku returns a timeout). Worker dynos run background jobs with no time limit (used for long-running processes, queue processing). One-off dynos are for ad-hoc tasks (database migrations, scripts). Candidates run long-running jobs on Web dynos — the exam expects Worker dynos for async processing.
3. Add-ons vs Buildpacks — Services vs Build Configuration
Add-ons are third-party services attached to a Heroku app (Postgres database, Redis cache, monitoring tools) — they are provisioned and billed separately. Buildpacks are scripts that transform your code into a runnable slug at build time (Node.js buildpack installs npm packages, Python buildpack installs pip packages). Candidates confuse add-ons (runtime services) with buildpacks (build-time configuration).
Frequently Asked Questions
- What is the Salesforce Heroku Architect exam format?
- The Salesforce Heroku Architect exam has 60 multiple-choice questions, a 105-minute time limit, a 67% passing score, and a $200 fee ($100 retake). It tests the ability to architect Heroku applications integrated with Salesforce: platform services, security, performance, scalability, and the Salesforce-Heroku integration patterns.
- What are the highest-weight Heroku Architect exam sections?
- Heroku Architecture and Design (30%) and Salesforce-Heroku Integration (25%) together account for 55% of the exam. Understanding Heroku dynos, add-ons, Heroku Postgres, Heroku Connect for data synchronisation, and when to use Heroku vs. Salesforce Platform for different application requirements are the most heavily tested areas.
- What is Heroku Connect and why is it important for this exam?
- Heroku Connect is a managed data synchronisation service that syncs Salesforce data to a Heroku Postgres database in near real-time. It is a key integration pattern for Heroku-Salesforce architectures. The exam tests when to use Heroku Connect vs. direct API integration, how to configure sync mappings, and the limitations of Heroku Connect (API limits, sync latency, supported object types).
- When should an architect choose Heroku over Salesforce Platform?
- Heroku is preferred when you need: open-source language flexibility (Node.js, Python, Ruby, Java), high-volume public-facing web applications, complex compute workloads that exceed Salesforce governor limits, or when mixing Salesforce and non-Salesforce data sources. Salesforce Platform is preferred for CRM-centric applications, declarative automation, and when staying within the Salesforce ecosystem is a priority.
- What concepts do most Heroku Architect candidates get wrong?
- The most commonly misunderstood topics for the Heroku Architect exam are: (1) Heroku Connect — Bidirectional Sync Has Write Conflict Rules; (2) Dyno Types — Web vs Worker vs One-Off; (3) Add-ons vs Buildpacks — Services vs Build Configuration. Candidates are most confidently wrong on these — learn the distinctions early to avoid losing marks on questions you expect to get right.
- Why do most Heroku Architect candidates fail questions about Heroku Connect?
- Heroku Connect synchronises data between a Heroku Postgres database and Salesforce objects. By default it is unidirectional (Salesforce to Postgres). Enabling bidirectional sync introduces write conflicts when both sides update the same record. Candidates assume bidirectional sync just works — the exam expects knowledge of the "Salesforce wins" vs "database wins" conflict resolution setting and...
- Why do most Heroku Architect candidates fail questions about Dyno Types?
- Web dynos handle HTTP requests and must respond within 30 seconds (otherwise Heroku returns a timeout). Worker dynos run background jobs with no time limit (used for long-running processes, queue processing). One-off dynos are for ad-hoc tasks (database migrations, scripts). Candidates run long-running jobs on Web dynos — the exam expects Worker dynos for async processing.
- Why do most Heroku Architect candidates fail questions about Add-ons vs Buildpacks?
- Add-ons are third-party services attached to a Heroku app (Postgres database, Redis cache, monitoring tools) — they are provisioned and billed separately. Buildpacks are scripts that transform your code into a runnable slug at build time (Node.js buildpack installs npm packages, Python buildpack installs pip packages). Candidates confuse add-ons (runtime services) with buildpacks (build-time co...
Related Exam Tips
Start Heroku Architect Prep
After this exam, consider Application Architect or System Architect next.