Salesforce Certified Heroku Architect (SP24): Preparation and Scheduling Guide
The Salesforce Certified Heroku Architect credential validates architectural judgment across scalable Heroku solutions, application deployment and operations, teams, build workflows, security, add-ons, and Salesforce integration. It is aimed at experienced Heroku practitioners, including consultants and partners, rather than candidates who have only memorized product terms. This guide helps you make a practical decision: whether your current experience is broad enough to schedule the exam now, or whether you should first close specific gaps through the official Salesforce material and hands-on architecture practice.
What the certification is designed to validate
The credential tests whether you can make and defend Heroku architecture decisions across the application lifecycle, not merely describe isolated platform features. Salesforce describes certified Heroku Architects as people skilled in architecting scalable solutions, deploying and managing apps, and managing teams and build workflows on Heroku.
The official exam description emphasizes designing, building, deploying, scaling, managing, and operating Heroku apps, teams, and build infrastructure. That combination matters. A candidate may know how to deploy an app yet still be unprepared to choose an appropriate runtime, organize delivery responsibilities, secure connectivity, or integrate Heroku with Salesforce data.
Treat the exam as an assessment of connected decisions. For example, an architecture discussion may require you to relate application design to deployment workflow, add-on selection, data movement, security controls, and operational management. Your preparation should therefore move from feature recognition toward explaining why one design is suitable under a stated requirement.
The “SP24” label in this guide identifies the exam version requested for this page. Because version details and availability can change, confirm the current credential and scheduling information through Salesforce before registering. The official credential page identifies the certification as “Salesforce Certified Heroku Architect.”
Who should consider scheduling it
Schedule only when your experience matches the exam’s intended profile and your weaker domains have been deliberately reviewed. Salesforce states that the exam is intended for candidates with a minimum of two years of experience and skills across the Heroku domains, and describes the target audience as Heroku Consultants or Partners with knowledge of application-development best practices, scalable Heroku apps, use cases, and Heroku best practices.
The stated experience areas include Heroku app development and deployment, scalable-solution architecture, Elements Marketplace add-ons, Heroku Postgres, Heroku Key-Value Store, Dataclips, and Heroku Connect. They also include Private Space Peering, VPN connections, Private Space Runtime versus Common Runtime, Heroku Enterprise, Heroku Shield, and Enterprise Teams.
This is a broad profile. Someone who works mainly on application code should not assume that coding familiarity covers enterprise account structure, network connectivity, security, or operational governance. Conversely, an administrator who has not designed or deployed scalable Heroku applications may need practical architecture work before relying on platform administration knowledge.
Use a readiness check before selecting a date. Write down one recent or simulated design for each major area: application architecture, delivery, scaling, security, data, integration, and team governance. If your notes contain product names but not trade-offs, dependencies, failure considerations, or reasons for selection, continue studying rather than treating recognition as readiness.
Which knowledge areas deserve the earliest attention
Begin with the areas that connect several other domains: enterprise architecture, application lifecycle management, security and trust, data and integration, and scalability. Salesforce’s description specifically calls out Heroku Enterprise, security and trust options, add-ons such as Heroku Postgres and Apache Kafka on Heroku, and integration with Salesforce data through database, API, and event systems, including Heroku Connect.
A useful order is to establish the platform boundary first, then design the application, then connect data and services, and finally plan delivery and operations. This prevents a common study error: learning individual services without understanding the architectural problem each service solves.
Your first pass should answer these questions in your own words:
• When would an enterprise arrangement be appropriate?
• What security and trust choices affect the design?
• How do Private Space Runtime and Common Runtime differ in an architecture decision?
• Where do Private Space Peering and VPN connections fit?
• Which requirement points toward a database, API, or event integration?
• What does a scalable, operationally manageable application require beyond adding capacity?
Do not infer that every listed experience area receives equal emphasis. The supplied official research identifies subject areas but does not provide verified domain percentages for this version. Avoid building a study schedule around unsupported weights; use breadth, risk, and your own experience gaps instead.
Enterprise, security, and networking
Review the purpose of Heroku Enterprise, Enterprise Teams, Heroku Shield, Private Space Runtime, Common Runtime, Private Space Peering, and VPN connections as related architectural choices. The goal is not to recite a catalogue. Practice mapping a business or technical requirement to the relevant control, boundary, or operating model.
For each topic, record the problem it addresses, what it changes in the architecture, which teams own it, and what assumptions must be confirmed. This approach makes similar-sounding options easier to distinguish and prepares you to reason about security and trust rather than memorize labels.
Application architecture and operations
Connect the Twelve-Factor App methodology with app design, deployment, scaling, monitoring, and operational ownership. Include microservices architectures in your review, but do not treat microservices as an automatic improvement. Practice identifying when separation helps and when it adds coordination, deployment, or observability responsibilities.
Include dynos, release management, build infrastructure, monitoring, and metrics in the same study block. The official preparation trailmix lists these subjects alongside Heroku architecture, Heroku Flow for Lifecycle Management, GitHub integration, continuous delivery and integration, Node.js, and Heroku Enterprise Basics.
Data, add-ons, and Salesforce integration
Study add-ons as architectural building blocks with operational consequences. The official exam description highlights Elements Marketplace add-ons, Heroku Postgres, Heroku Key-Value Store, Dataclips, Apache Kafka on Heroku, and Heroku Connect. For each, explain the workload or integration need it serves, how it participates in the design, and what must be managed after deployment.
Separate database, API, and event-based integration in your notes. Salesforce specifically says the exam covers integrating Heroku applications with Salesforce data through those systems, including Heroku Connect. A strong preparation exercise is to design three versions of the same integration requirement and explain why the chosen mechanism changes with data freshness, coupling, ownership, and operational needs.
How to use the official preparation material
Use Salesforce’s preparation trailmix as a syllabus, then turn each item into an architecture exercise. The trailmix includes Heroku Enterprise Basics, Heroku Flow for Lifecycle Management, Heroku architecture, monitoring and metrics, GitHub integration, dynos, Node.js, continuous delivery and integration, and release management.
Do not complete a module passively and mark the topic finished. After each unit, produce a short decision record containing four parts: the requirement, the candidate design, the reason for choosing it, and the risk or assumption that remains. This creates a revision resource that reflects architectural judgment rather than copied definitions.
A practical sequence is:
1. Review Heroku Enterprise Basics and the major runtime and governance concepts.
2. Study Heroku architecture, the Twelve-Factor App methodology, dynos, and scaling relationships.
3. Work through lifecycle management, GitHub integration, continuous delivery and integration, and release management.
4. Add monitoring and metrics to every design so that operation is considered before deployment.
5. Study data services, add-ons, Kafka, Heroku Connect, and Salesforce integration as connected choices.
6. Return to security, networking, teams, and build infrastructure to test whether your design is suitable for an enterprise setting.
The official Salesforce preparation trailmix is the right starting point for coverage. It is not a substitute for checking current product documentation or verifying any version-specific exam information before you schedule.
A four-phase study roadmap
A staged plan is more effective than repeatedly rereading the same product pages. Use four phases: baseline, architecture construction, integration and operations, and decision rehearsal. The length of each phase should reflect your experience; the official sources supplied here do not establish a required preparation duration.
Phase one is a gap assessment. Read the official credential description and list every named experience area. Mark each as strong, familiar, or weak, then support the rating with evidence such as a project, design document, deployment task, or completed learning unit. “I have heard of it” belongs in the weak category, not the familiar category.
Phase two builds a reference architecture. Create a solution that includes an application, deployment workflow, data service, external integration, observability, security boundary, and team responsibilities. Explain how the components interact and what happens during a release, failure, scale change, or rollback. Revisit the design after studying each relevant official topic.
Phase three isolates integration and operations. Create separate designs for database, API, and event integration with Salesforce data. Add Heroku Connect where it is appropriate to the scenario, and include Apache Kafka on Heroku when an event-oriented design is justified. Then document ownership of data, delivery, monitoring, access, and incident response.
Phase four is decision rehearsal. Give yourself a requirement such as regulated data, multiple delivery teams, a need for scalable services, or a Salesforce-connected application. Without looking at notes, choose the runtime and connectivity model, application structure, add-ons, delivery workflow, and governance approach. Afterwards, check every choice against official material and record what you missed.
Finish the roadmap with a readiness review rather than a confidence estimate. You are closer to scheduling when you can explain alternatives, identify assumptions, and connect a requirement to a coherent design across the named domains.
What to build as a practical study project
Build a small reference solution or detailed design that forces the major domains to meet. The project does not need to reproduce a production system. Its purpose is to make you decide how an application is developed, deployed, secured, integrated, scaled, monitored, and governed.
Start with a Heroku application that has a clear business function and a Salesforce data dependency. Select a data path and state why it is database-based, API-based, event-based, or uses Heroku Connect. Add a second service only when the requirement justifies it; this gives you a reasoned opportunity to discuss a microservices boundary rather than adding components for appearance.
Next, define the delivery path. Show the source repository, build process, release management steps, environment separation, approval responsibilities, and rollback considerations. The official trailmix’s coverage of GitHub integration, Heroku Flow for Lifecycle Management, continuous delivery and integration, and release management gives you a useful checklist for this part.
Then add the operational layer. Describe the dyno arrangement at a conceptual level, expected scaling pressure, metrics to watch, ownership of alerts, and the response to a failed release or unhealthy dependency. Avoid inventing platform behavior that you have not verified. The exercise is about disciplined reasoning and documentation, not creating unsupported specifications.
Finally, produce two variants of the design: one using Common Runtime and one using Private Space Runtime. Explain which security, connectivity, trust, or governance requirement would make the second variant appropriate. Include Private Space Peering or a VPN connection only when you can explain the architectural need and responsibility associated with it.
How to study scenario-based architecture decisions
Practice answering every scenario in a fixed order: identify the requirement, classify the constraint, list viable options, eliminate mismatches, choose the design, and state the trade-off. This method keeps you from selecting a familiar feature before understanding whether the scenario is about security, scale, integration, delivery, or governance.
For a requirement involving Salesforce data, first determine the interaction pattern. A request for synchronized data access is a different design problem from an external API transaction or an event-driven response. The official exam description names database, API, and event systems, as well as Heroku Connect, so your reasoning should distinguish them instead of treating “Salesforce integration” as one undifferentiated topic.
For an enterprise security scenario, identify the boundary and the trust relationship before discussing implementation details. Ask whether the requirement concerns runtime isolation, private connectivity, account governance, data protection, or team access. Then relate the answer to the relevant Heroku Enterprise, Heroku Shield, Enterprise Teams, Private Space, peering, or VPN concept that you have verified in your study.
For a delivery scenario, trace the change from source control through build, release, deployment, monitoring, and ownership. Include the human workflow as well as the technical path. Salesforce’s description includes managing teams and build workflows, so an answer that discusses only application code is incomplete.
After each practice scenario, write one reason your chosen option is better than the nearest alternative. This single step exposes shallow memorization quickly and helps you notice when a design depends on an unstated assumption.
Mistakes that weaken otherwise solid preparation
The most damaging mistake is studying the platform as a list of product names. A candidate may recognize Heroku Postgres, Kafka, Heroku Connect, Shield, or Private Spaces yet fail to explain when the option fits the requirement. Replace lists with decision tables that show purpose, dependencies, ownership, and trade-offs.
Another mistake is overconcentrating on application development. Salesforce explicitly includes teams, build workflows, enterprise use, security and trust, operations, and integration. If your preparation contains no account, network, governance, monitoring, or release exercises, it does not reflect the full stated scope.
Do not assume that a scalable design is simply a larger deployment. Review architecture, the Twelve-Factor App methodology, microservices architectures, dynos, monitoring, metrics, and lifecycle management together. Scaling must be considered alongside configuration, dependencies, data behavior, deployment safety, and observability.
Avoid treating Common Runtime and Private Space Runtime as interchangeable labels. Build a comparison based on the requirements in a scenario, especially connectivity, trust, and enterprise governance. Use official documentation to verify details rather than relying on old notes or an informal comparison.
Do not memorize from dumps or leaked-question claims. Such material cannot establish architectural understanding, may be inaccurate or outdated, and does not make a passing result certain. Use official Salesforce learning and credential information, then test yourself with original scenarios that you have written from the published domains.
Finally, do not schedule because one familiar domain feels strong. The stated candidate profile spans multiple Heroku domains. A readiness decision should be based on demonstrated coverage across the weak areas, not confidence produced by repeated review of one feature set.
What delivery information is officially confirmed
Salesforce states that proctored certification exams can be delivered online through Pearson OnVUE or in person at a Pearson VUE testing center. Confirm the current appointment choices, policies, identification requirements, and technical or site instructions through the official certification and scheduling channels before booking.
The supplied official research does not verify the exam price, duration, question count, passing score, languages, rescheduling rules, or a current retirement date. Do not rely on an old preparation page or a third-party listing for those details. Check the current Salesforce credential information and the relevant Pearson VUE scheduling information when you are ready to register.
A sensible scheduling decision has two parts. First, confirm that the official listing still corresponds to the version you intend to take. Second, choose the delivery option that you can satisfy operationally, including the requirements shown during the official booking process. This is a practical recommendation, not an additional Salesforce requirement.
Salesforce’s Trailhead material also includes certification maintenance resources, including an official module titled “Heroku Architect Certification Maintenance (Summer ’24)” and a “Heroku Architect Certification Maintenance (Summer ’25)” module. These resources indicate that maintaining certification is a separate consideration from preparing for the initial exam. Check the current maintenance requirement rather than assuming a past cycle applies unchanged.
How to decide whether to book now
Book when you can independently produce a defensible architecture across the published domains and can explain why alternatives do not fit. If you still confuse runtime choices, cannot separate database, API, and event integration, or have no working model for teams and build workflows, postpone registration and target those gaps first.
Use this final review:
• Can you describe the purpose and trade-offs of the Twelve-Factor App methodology and microservices architectures?
• Can you connect app development, deployment, scaling, monitoring, and release management in one lifecycle?
• Can you explain when Heroku Enterprise and its security and trust options matter?
• Can you distinguish the role of Heroku Postgres, Heroku Key-Value Store, Dataclips, Heroku Connect, and other relevant add-ons in an architecture?
• Can you reason about Private Space Runtime, Common Runtime, Private Space Peering, and VPN connections from requirements rather than preference?
• Can you design Salesforce integration through database, API, and event systems and explain where Heroku Connect fits?
• Can you assign responsibilities for teams, build infrastructure, releases, and operations?
If several answers are uncertain, convert each uncertainty into a study task with a written output. If you can answer them but cannot support the reasoning with a design exercise, perform one more architecture rehearsal. Schedule only after both knowledge coverage and decision practice are credible.
Actions to take before registration
Start with the official credential page and the official Salesforce exam description, then open the preparation trailmix. Confirm the credential name, review the listed experience areas, and note any current information that differs from older SP24 material. This verification step prevents a preparation plan from being built around stale assumptions.
Next, create a one-page gap matrix. Put enterprise and security, application architecture, deployment and lifecycle, add-ons and data, Salesforce integration, networking, and operations in separate rows. For every row, record the official learning item you will use, the design exercise you will complete, and the evidence that the gap is closed.
Complete the Trailhead material actively. After each topic, update your reference architecture and decision notes. Use the official maintenance resources separately so that preparation for the exam is not confused with post-certification maintenance.
When the gap matrix is complete, check the current delivery details through Salesforce. Decide between the officially stated online Pearson OnVUE option and an in-person Pearson VUE testing center only after confirming the current appointment requirements. Keep a final review focused on trade-offs and architecture decisions rather than attempting to memorize unsupported exam statistics.
The result you want is not a longer list of terms. It is a compact set of designs and explanations showing that you can connect scalable Heroku applications, enterprise controls, deployment workflows, data services, Salesforce integration, and operational ownership into a coherent solution.
Conclusion
The Salesforce Certified Heroku Architect exam is best approached as a breadth-and-judgment assessment. Use the official Salesforce description to map the domains, use the Trailhead preparation trailmix to organize learning, and use original architecture exercises to test whether you can make connected decisions. Confirm current version, appointment, and maintenance information before acting because those details can change. If your study notes explain requirements, alternatives, ownership, and trade-offs across the published areas, you have a sound basis for deciding whether to schedule.
Related exams
- Analytics-Arch-201 exam — Salesforce Certified Tableau Architect
- B2B-Solution-Architect exam — Salesforce Certified B2B Solution Architect
- B2C-Commerce-Architect exam — Salesforce Certified B2C Commerce Architect
- B2C-Solution-Architect exam — Salesforce Certified B2C Solution Architect
- Mobile-Solutions-Architecture-Designer exam — Salesforce Certified Mobile Solutions Architecture Designer
- Sharing-and-Visibility-Architect exam — Salesforce Certified Sharing and Visibility Architect
