Heroku-Architect
Salesforce Certified Heroku Architect
Salesforce Certified Heroku Architect (SP24): Exam Guide and Study Roadmap
The Salesforce Certified Heroku Architect credential validates architectural judgment across scalable Heroku applications, deployment and operations, enterprise controls, add-ons, and integration with Salesforce data. It serves experienced Heroku practitioners, including consultants and partners, who must choose suitable platform patterns rather than recall isolated commands. This guide helps you decide whether your experience is ready for the SP24 exam, which knowledge gaps to close first, how to organize practical study, and what to verify before scheduling a proctored attempt.
What does the Salesforce Certified Heroku Architect exam validate?
The exam validates whether you can make and defend architecture decisions for Heroku applications and the teams and build infrastructure that support them. It is broader than application coding: Salesforce describes the role as architecting scalable solutions, deploying and managing apps, and managing teams and build workflows on Heroku.
The official exam description is aimed at candidates with knowledge, skills, and extensive experience designing, building, deploying, scaling, managing, and operating Heroku apps, teams, and build infrastructure. It also states that the exam is intended for candidates with a minimum of two years of experience across the Heroku domains. Those statements are useful readiness tests, not a substitute for reading the current credential information before booking.
Salesforce lists Heroku Consultants or Partners as a target audience. The expected profile includes application-development best practices, scalable Heroku applications, Heroku use cases, and Heroku best practices. A candidate who has only followed tutorials but has not made trade-offs around security, integration, operations, and team governance should treat that as a preparation gap.
The credential is listed by Salesforce as “Salesforce Certified Heroku Architect.” The SP24 label in this guide identifies the exam version requested; candidates should confirm the current exam and maintenance information on the official credential page before scheduling. Source: https://trailhead.salesforce.com/credentials/herokuarchitect
Which skills should shape the study plan?
Study by architectural capability, not by a loose list of Heroku product names. The official material groups the useful experience areas around application architecture and delivery, enterprise networking and security, add-ons and data, Salesforce integration, and operational decision-making. Your study notes should connect each technology to a problem, constraint, and reason for selecting it.
The supplied official research does not provide domain percentages or a percentage-based exam blueprint. Do not assign unofficial weights to the domains or compare bare percentages. Instead, use the full capability set below to identify weak areas and spend additional time where you cannot explain a design choice clearly.
Application architecture and delivery includes Heroku app development and deployment, scalable-solution architecture, the Twelve-Factor App methodology, microservices architectures, dynos, build infrastructure, continuous delivery and integration, release management, monitoring, and metrics. Prepare to reason about how an application is built, released, scaled, observed, and operated as a system.
Platform and enterprise architecture includes knowing when to use Heroku Enterprise and understanding the security and trust options available in Heroku and Heroku Enterprise. The listed experience areas include Enterprise Teams, Heroku Shield, Private Space Runtime versus Common Runtime, Private Space Peering, and VPN connections.
Data, messaging, and extensions includes Elements Marketplace add-ons, Heroku Postgres, Heroku Key-Value Store, Dataclips, and Apache Kafka on Heroku. The official description specifically calls out using add-ons to extend applications, particularly Heroku Postgres and Apache Kafka on Heroku.
Salesforce connectivity includes integrating Heroku applications with Salesforce data through database, API, and event systems, including Heroku Connect. The listed experience also includes integration with the Salesforce Lightning Platform. Your preparation should therefore cover more than a single synchronization product; it should compare integration approaches against data direction, latency, ownership, and operational needs without assuming one tool fits every scenario.
For each capability, write a short decision record with four parts: the requirement, the candidate architecture, the rejected alternative, and the operational consequence. This converts product familiarity into the judgment the role calls for. Source: https://help.salesforce.com/s/articleView?id=005298948&language=en_US&type=1
How can you judge whether your experience is sufficient?
You are closer to exam readiness when you can explain a Heroku architecture from requirements through operation, including why the selected runtime, network boundary, add-ons, integration method, deployment workflow, and governance model fit the situation. Familiarity with individual commands is not enough if you cannot discuss failure handling, scaling, security, and ownership.
Use the following diagnostic before beginning a full study cycle. For each prompt, answer from memory, then verify the explanation against Salesforce and Heroku documentation. Mark a topic as weak if your answer is a product definition without a design rationale.
For an application design, can you describe how Twelve-Factor principles and a microservices approach affect configuration, dependencies, release boundaries, and operational responsibility? Can you distinguish a decomposition that improves independent delivery from one that merely adds network calls and coordination?
For delivery, can you trace code from source control through build, test, release, configuration, rollback, and monitoring? Can you identify which team owns each stage and what evidence would show that a release is healthy? The official preparation trailmix includes Heroku Flow for Lifecycle Management, GitHub integration, continuous delivery and integration, and release management, so these are sensible areas for structured review.
For runtime and enterprise controls, can you explain the architectural consequences of choosing Private Space Runtime or Common Runtime? Can you reason about Private Space Peering, VPN connections, Heroku Enterprise, Heroku Shield, and Enterprise Teams in terms of connectivity, trust, administration, and workload requirements?
For data and integration, can you choose among Heroku Postgres, Heroku Key-Value Store, Dataclips, Heroku Connect, APIs, and event systems based on the role each component plays? Can you describe what happens when data is delayed, duplicated, unavailable, or owned by another system?
For teams and operations, can you explain how access, build workflows, application management, monitoring, and incident response fit together? If you cannot answer a prompt without searching, record it as a study objective rather than scheduling immediately.
What should you study first?
Start with the architecture foundations that influence every later decision, then move into delivery and operations, followed by enterprise security and networking, and finish with data, messaging, and Salesforce integration. This sequence prevents a common mistake: memorizing add-ons before understanding the workload and governance requirements they must serve.
First, review the Twelve-Factor App methodology, scalable application architecture, microservices trade-offs, dyno-based application operation, and the separation of configuration from code. Build a one-page architecture sketch showing application components, dependencies, configuration, data stores, and external services. Add the expected traffic pattern, availability needs, and operational owner even when the source scenario is brief.
Next, study the delivery path. The official preparation trailmix includes Heroku Enterprise Basics, Heroku Flow for Lifecycle Management, monitoring and metrics, GitHub integration, dynos, Node.js, continuous delivery and integration, and release management. Use those subjects as a checklist, but do not treat completion of a learning item as proof that you can solve an architecture scenario.
Then cover enterprise organization and trust boundaries. Review the purpose of Heroku Enterprise, Enterprise Teams, Heroku Shield, Private Space Runtime, Common Runtime, Private Space Peering, and VPN connections. For each, write what requirement would make it relevant and what additional operational or design consideration it introduces. Keep the descriptions tied to the use case rather than learning them as disconnected labels.
After that, work through extensions and data. Put Heroku Postgres, Heroku Key-Value Store, Dataclips, and Apache Kafka on Heroku into a comparison table containing role, data characteristics, access pattern, scaling concern, and failure consideration. The table is a study aid you create; it is not an official exam blueprint.
Finish with Salesforce integration. Compare database, API, and event approaches, including Heroku Connect, and map each approach to synchronization direction, freshness requirement, ownership, transformation, error handling, and monitoring. The objective is to explain a suitable integration boundary, not to select a named product automatically.
How should you turn product knowledge into architecture practice?
Use scenario-based design exercises with explicit constraints. Each exercise should require a recommendation, an alternative, and a risk treatment. This is more valuable than rereading feature descriptions because the credential is aimed at people who architect scalable solutions and manage delivery and operations.
Create a scenario involving a Heroku application that must connect to Salesforce data. Define whether the application reads, writes, or synchronizes data; identify which system owns each record; and state how quickly a change must become visible. Compare a database approach, an API approach, an event approach, and Heroku Connect where relevant. For every option, record the consequences for retries, ordering, duplicate handling, schema change, access control, and observability.
Create a second scenario involving an enterprise team with separate development and production responsibilities. Draw the account, team, application, build, release, and monitoring relationships. Identify where permissions should be limited, which workflow stages require approval, and how an incident would be investigated. This exercise makes Enterprise Teams and Heroku Enterprise part of a governance design rather than vocabulary memorization.
Create a third scenario involving an application that must scale while preserving safe releases. Start with a Twelve-Factor design, then identify service boundaries, configuration sources, data dependencies, build steps, release steps, and health signals. Ask whether a microservices split reduces an actual bottleneck or simply increases operational complexity. Explain how you would detect a bad release and what rollback decision would follow.
Create a fourth scenario involving private connectivity. State why the workload requires a private boundary, what systems must communicate, and whether the design needs Private Space Peering or a VPN connection. Include the difference between a private runtime choice and a general application deployment choice. The point is not to invent a universal answer; it is to make the network requirement explicit before selecting a control.
After each exercise, perform a review in three passes. First, check factual terminology against official documentation. Second, challenge the architecture with a failure or growth condition. Third, rewrite the recommendation in a concise form that names the requirement, choice, trade-off, and operating responsibility.
What mistakes make Heroku Architect preparation inefficient?
The largest preparation mistake is treating the exam as a command-recall test. An architect must connect platform features to requirements, risks, and operating models. Replace lists of definitions with diagrams, decision tables, and short written justifications that reveal whether you understand the consequences of a choice.
A second mistake is studying Common Runtime, Private Space Runtime, Enterprise, Shield, peering, and VPN connections as interchangeable security terms. They address different architectural and governance questions. Put each in a scenario and ask what must be protected, what must connect, who administers it, and what operational boundary the design requires.
A third mistake is reducing Salesforce integration to Heroku Connect. Salesforce’s official description includes database, API, and event systems, including Heroku Connect. Prepare to select an integration style according to ownership, latency, coupling, volume, and recovery needs. A named tool is not an answer until the data movement and failure behavior are explained.
A fourth mistake is treating add-ons as automatic architecture decisions. Elements Marketplace add-ons, Heroku Postgres, Heroku Key-Value Store, Dataclips, and Apache Kafka on Heroku have different roles. For each one, learn the problem it addresses, the application interaction it enables, and the operational questions it creates. Avoid writing unsupported limits or performance claims into your notes.
A fifth mistake is separating build and release study from application architecture. The official preparation trailmix includes Heroku Flow for Lifecycle Management, GitHub integration, continuous delivery and integration, and release management because delivery is part of operating a scalable solution. Include code promotion, configuration, testing, release visibility, monitoring, and rollback in the same design exercise.
A sixth mistake is relying on leaked questions or exam dumps. They do not establish understanding, can be inaccurate or unauthorized, and cannot replace official preparation. Use legitimate documentation, Trailhead learning, and your own scenario analysis instead. No memorization source guarantees a pass.
A final mistake is ignoring credential maintenance. Salesforce provides a Heroku Architect Certification Maintenance module for Summer ’24 and a module titled Heroku Architect Certification Maintenance (Summer ’25). These resources show that maintenance learning exists, but they do not by themselves establish the current status or requirements for the SP24 exam. Verify the applicable requirement on Salesforce before and after certification.
What four-week study roadmap is practical?
A four-week plan works when each week produces an artifact you can review, not merely a larger pile of notes. Adjust the pace to your experience and available time; the official sources provided here do not establish a required study duration or a guaranteed preparation schedule.
Week one: establish the architecture baseline. Review scalable Heroku application design, the Twelve-Factor App methodology, microservices architectures, dynos, and the application lifecycle. Draw one reference architecture and write decision records for configuration, service boundaries, data dependencies, and operational ownership. End the week by explaining the design without reading from your notes.
Week two: build delivery and operations fluency. Work through the preparation trailmix topics covering Heroku Flow for Lifecycle Management, GitHub integration, continuous delivery and integration, release management, monitoring and metrics, and build workflows. Trace a hypothetical change from commit to production observation. Add failure cases for a failed build, a failed release, an unhealthy application, and an incomplete rollback.
Week three: focus on enterprise architecture and platform extensions. Study Heroku Enterprise, Enterprise Teams, Heroku Shield, Private Space Runtime, Common Runtime, Private Space Peering, VPN connections, and the relevant add-ons. Produce a comparison matrix based on requirements and governance. Then review Heroku Postgres, Heroku Key-Value Store, Dataclips, and Apache Kafka on Heroku in application scenarios rather than isolated flashcards.
Week four: integrate Salesforce connectivity and assess readiness. Design several end-to-end solutions using database, API, event, and Heroku Connect patterns where appropriate. For each, describe ownership, data freshness, authentication and access considerations, retries, monitoring, and operational escalation. Finish with a timed, distraction-free review using original scenarios. Do not treat a high score on an unofficial question bank as proof of readiness; judge whether you can defend each architecture decision.
At the end of every week, maintain a gap list with three labels: factual gap, design gap, and communication gap. A factual gap means you cannot describe a platform capability accurately. A design gap means you know the capability but cannot choose it under constraints. A communication gap means your recommendation is correct but does not clearly state trade-offs or operational consequences. Address design gaps first when the exam is near.
How can the official Trailhead resources be used effectively?
Use the official preparation trailmix as a navigation aid, then supplement it with architecture exercises and current Salesforce documentation. Trailhead can organize the learning sequence, but completing a module does not demonstrate that you can compare architectures, identify risks, or manage the resulting solution.
Salesforce provides an official Trailhead preparation trailmix for the Heroku Architect certification. Its listed preparation subjects include 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. Start with the items closest to your weakest diagnostic area rather than consuming the trailmix passively.
Use the official credential page to confirm the credential name and review current certification information. Use the Salesforce Help exam description to validate the audience and experience expectations, the listed technology areas, and the scope of architecture, operations, security, add-ons, and integration. Keep a separate note for information that is officially stated and information that is your own study recommendation.
Salesforce also lists a Heroku Architect Certification Maintenance (Summer ’24) module and provides a Heroku Architect Certification Maintenance (Summer ’25) module. Treat maintenance content as lifecycle information that may matter after certification, not as a replacement for preparation for the requested exam version. Check the applicable Salesforce page for the current requirement.
A second Trailmix is titled Salesforce Certified Heroku Architecture Designer. It may provide additional learning navigation, but do not infer from its title that every item is a current exam requirement. Cross-check any time-sensitive or exam-specific claim against the credential and Help pages.
What delivery details should you verify before scheduling?
Salesforce states that proctored certification exams can be delivered online through Pearson OnVUE or in person at a Pearson VUE testing center. That establishes the available delivery channels in the supplied research, but candidates should verify current appointment, identification, environment, and policy details through the official Salesforce and Pearson VUE scheduling flow before selecting a date.
Choose the delivery method only after checking practical constraints. For online delivery, confirm that your workspace, equipment, network, and identification meet the current proctoring requirements. For a testing center, verify location, appointment availability, arrival instructions, and permitted items. These are scheduling checks, not assumptions about the exam itself.
Do not rely on an old forum post for current delivery rules, registration conditions, fees, exam duration, question count, passing score, languages, or availability. None of those details is established by the supplied verified facts. If a detail affects your booking decision, look for it on the current official credential or scheduling page and record the date on which you checked it.
The supplied Trailhead pages contain the statement “Register three or more to unlock $999 passes.” That is a promotional statement shown in the provided source material, not a general exam price, scheduling requirement, or entitlement that should be assumed to apply to an individual candidate. Confirm eligibility and current terms directly from Salesforce if it is relevant to your organization.
How should you make the final readiness decision?
Schedule when you can consistently solve unfamiliar architecture scenarios and explain the reasoning behind your choices across application design, delivery, enterprise controls, extensions, data, Salesforce integration, and operations. Do not schedule merely because you have finished a Trailhead list or memorized product names.
Use a final readiness review with one scenario for each major capability. For application architecture, defend a scalable design and explain Twelve-Factor and microservices implications. For delivery, describe build, release, monitoring, and rollback responsibilities. For enterprise architecture, justify runtime, connectivity, security, and team-governance choices. For data and extensions, select suitable services and state their operational implications. For Salesforce integration, explain why database, API, event, or Heroku Connect patterns fit the data requirements.
Ask a colleague to challenge every recommendation with one new constraint: stricter trust boundaries, higher change frequency, delayed data, a failed dependency, a larger team, or a requirement for independent service delivery. If your answer changes, write down the principle that changed it. This is more revealing than repeating the same familiar lab.
Delay scheduling if you repeatedly confuse product roles, cannot explain data ownership, omit failure handling, or choose security and networking features without a stated requirement. Those are architecture gaps, not minor terminology issues. Return to the relevant official source, update your decision records, and repeat the scenario with a different set of constraints.
Before booking, verify the current credential listing, the applicable exam version, delivery channel, and scheduling rules from official Salesforce pages. After booking, reserve the remaining study time for targeted gap correction rather than starting an unrelated resource collection.
What should you do after the exam attempt?
Use the result and your preparation artifacts to guide the next step. If you pass, review Salesforce maintenance information so the credential remains current under the applicable rules. If you do not pass, convert the result and remembered topic areas into a targeted gap plan without seeking or sharing protected exam content.
A successful result is not the end of the skill set described by Salesforce. Continue practicing architecture reviews that connect scalable applications, deployment and management, teams, build workflows, enterprise controls, add-ons, data stores, messaging, and Salesforce integration. The same decision records used for study can become design-review templates for real projects.
If the attempt is unsuccessful, separate weak knowledge from weak scenario reasoning. Revisit official material for factual uncertainty, then create new scenarios that change the constraints. Do not simply repeat a question bank or memorize answer patterns. The goal is transferable architectural judgment, and unauthorized exam content cannot provide a reliable substitute for it.
Finally, check Salesforce’s current certification and maintenance pages rather than assuming an older version’s rules continue unchanged. The official credential page and maintenance modules are the appropriate starting points for that check.
Conclusion
The Salesforce Certified Heroku Architect exam is best approached as an architecture decision exercise covering the whole Heroku operating model. Confirm that your experience matches Salesforce’s intended audience, study the capabilities as connected design concerns, practice with constraints and failure conditions, and verify current scheduling and maintenance information from official sources. Your next action should be a diagnostic architecture review: choose one Heroku-to-Salesforce scenario, document the alternatives and trade-offs, and use the gaps it exposes to set your study sequence.
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