Heroku-Architect Practice Exam - Salesforce Certified Heroku Architect

Salesforce Certified Heroku Architect: Exam Overview and 2026 Certification Path

I've watched the Salesforce certification space evolve for years, and honestly, the Salesforce Certified Heroku Architect credential? It's one of the most underrated paths if you're serious about enterprise cloud architecture. This isn't just another cert to add to your LinkedIn. The thing is, this one actually validates that you can design and run production-grade applications on Heroku at scale, not just talk about it at happy hour.

What this credential proves you know

Real talk here. The Heroku Architect certification demonstrates you've got deep expertise in building enterprise applications on the Heroku platform. We're talking scalable, secure, highly available solutions that actually work when the CFO's dashboard needs to load during an investor call, not just during your demo to the team.

Look, anyone can spin up a dyno. I mean, my cousin did it last weekend. But this cert validates you understand Heroku runtime environments, data services like Heroku Postgres, and the operational practices that separate a hobby project from something that handles millions in revenue. You'll need to show you can implement security controls and compliance frameworks. Not just check boxes to make your boss happy, but actually design governance policies that keep auditors nodding and data safe.

The networking piece? Huge here. Private Spaces, VPC peering, connectivity patterns. If those words make you nervous, you're not ready yet. You also need to prove mastery of CI/CD pipelines and DevOps workflows specific to Heroku, which honestly feels different than traditional cloud platforms (though maybe that's just me).

Disaster recovery matters. High availability architectures too. Yeah, they want to know you can design systems that don't fall over when AWS has a bad day in us-east-1, which seems to happen more often than Amazon admits. Plus monitoring, logging, troubleshooting production apps, because 3 AM incidents don't care about your certification status or your kid's soccer game tomorrow.

Cost optimization's on there too. Heroku can get expensive fast if you don't know what you're doing. Finance teams notice when the monthly bill doubles because someone left performance dynos running over the weekend. I once saw a dev rack up $8K in charges during a three-day weekend because they forgot to scale down after load testing. That's a conversation nobody wants to have.

Who should actually pursue this in 2026

Senior Heroku developers with 3+ years hands-on experience? Obvious candidates. Not gonna lie, if you've only been playing with Heroku for six months, you'll struggle with the depth this exam demands. Maybe come back later.

Solution architects designing cloud-native applications for enterprise clients will find this credential opens doors. Same for technical leads who are responsible for Heroku infrastructure and operations. It gives you the language and framework to justify architectural decisions to stakeholders who think "the cloud" is just someone else's computer.

Here's an interesting one: Salesforce architects expanding into full-stack development. If you're already crushing the Salesforce Certified Integration Architect credential, adding Heroku architecture makes you incredibly valuable because you understand both sides of the integration story. Most folks don't.

DevOps engineers managing Heroku deployment pipelines should consider this. Consultants advising clients on Heroku adoption and migration strategies basically need it to have credibility. Clients won't listen otherwise. Platform engineers building multi-tenant SaaS applications on Heroku will find the structured knowledge invaluable, even if they already know most of it from experience (though they probably have gaps they don't realize).

Security architects implementing compliance requirements on Heroku are another fit. Technical decision-makers evaluating Heroku for enterprise workloads can use this as due diligence. Honestly, nothing like prepping for an exam to expose what you don't actually know about a platform you thought you understood.

Career benefits that actually matter

Look, certifications aren't magic. But this positions you as a specialist in the growing Heroku ecosystem, which is smaller than AWS or Azure but way more focused. I've seen salary premiums of 15-25% over non-certified peers in the same roles, though obviously your mileage varies by market and company (and frankly, your negotiation skills).

It opens doors. Senior architect roles. Principal engineer positions. When I review resumes, seeing Heroku-Architect exam completion signals someone who invested in deep platform knowledge, not just surface-level familiarity you get from a weekend tutorial. That demonstrates commitment to professional development that hiring managers notice. Or at least the good ones do.

The credibility boost when consulting with clients or stakeholders? Real. You can say "I'm a Salesforce Certified Heroku Architect" and people actually understand that means something specific, not just that you read a blog post once. It provides competitive advantage in job markets where Heroku skills are required, and there are fewer qualified candidates than you'd think. That drives up your value.

The cert validates expertise recognized across the Salesforce partner ecosystem. It supports career progression from developer to architect-level positions in a structured way, giving you clear milestones. Plus it opens thought leadership opportunities through speaking and writing if that's your thing (though public speaking terrifies me personally).

How it fits the Salesforce ecosystem

The Heroku Architect certification complements the Salesforce Certified Application Architect credential beautifully. If you're already working toward or hold that cert, Heroku architecture fills in the full-stack picture instead of leaving gaps.

It builds upon the Heroku Architecture Designer certification, which is honestly the recommended prerequisite even if Salesforce doesn't strictly require it. Don't skip that one. The knowledge integrates perfectly with what you'd learn for the Integration Architect track, since you're dealing with many of the same integration patterns, just from a different angle.

This cert supports pursuit of the Salesforce Certified Technical Architect (CTA) credential. Several CTAs I know used their Heroku expertise as part of their review board presentations, and it apparently impressed the panelists. It fits with platform developer certifications like Salesforce Certified Platform Developer I by extending your skills beyond just Apex and Lightning into actual infrastructure concerns.

For folks holding Salesforce Certified Administrator or advanced admin credentials, this demonstrates you can go beyond configuration into actual architecture and code. Which is frankly where the interesting problems live. It pairs well with data architect knowledge too. Heroku Postgres HA strategies overlap with broader data architecture concepts you'll see elsewhere.

Basically? It positions you as a hybrid cloud architect across both platforms. That's increasingly valuable as enterprises run workloads across Salesforce core and Heroku rather than picking just one, which seems to be the trend lately.

2026 exam space and what's changed

The exam reflects latest Heroku platform features and architectural patterns. I mean, cloud platforms evolve fast, and the Salesforce Heroku-Architect exam content updates regularly to stay relevant. They're not testing you on stuff from 2018.

Recent iterations incorporated updated security and compliance requirements. GDPR, CCPA, SOC 2, all that fun regulatory stuff that keeps lawyers employed. There's new content on Heroku Fir, the next-generation runtime that's changing how dynos work under the hood in ways that'll affect your architecture decisions. You'll see questions addressing modern containerization and orchestration concepts even though Heroku abstracts a lot of that away, which feels a bit ironic honestly.

Cloud-native design patterns get emphasized. Microservices architectures too. More than in older versions, anyway. The integration scenarios now include Salesforce Functions and other newer services beyond just Heroku Connect, which had been the default answer for years. Expanded coverage of observability and monitoring tools reflects how critical that's become for production systems. You can't just deploy and pray anymore.

Cost optimization shows up more. Resource management practices too. Probably because enterprises finally realized their Heroku bills were getting out of control and someone had to explain why they spent $50K last quarter. The exam incorporates feedback from previous candidates. Salesforce actually listens to the community about what was unclear or outdated, which is refreshing.

It fits with industry trends in platform engineering and DevOps, not just Salesforce-specific patterns. That makes the knowledge more transferable if you ever move beyond the Salesforce ecosystem, though honestly once you're deep in it, that rarely happens. The ecosystem's like quicksand, but in a good way.

The exam still challenges you on fundamentals. Dyno types. Buildpacks. Routing mechanics. But the scenarios are more realistic and complex than they used to be. You can't just memorize documentation and expect to pass. You need to have architected real systems to understand the tradeoffs the questions explore, which honestly makes it a better certification.

Heroku Architect Certification Cost: Investment and Financial Planning

What the credential validates

The Salesforce Certified Heroku Architect credential is basically Salesforce saying you can design and defend an end-to-end Heroku solution that won't fall over the first time traffic spikes or a security team asks hard questions. It's architecture. Not button clicking.

It's not only about dynos. You're expected to understand the messy real stuff like Heroku Postgres high availability, secure networking, operational monitoring, and how Salesforce integration with Heroku actually behaves when auth tokens expire at 2 a.m. The exam wants opinions. Not yours. Heroku's.

Who should take the Heroku-Architect exam

This is for people who already ship apps on Heroku and have dealt with production incidents. If you've never had to reason about Heroku Private Spaces architecture connectivity, routing, and governance, you're going to feel the gap fast.

Consultants love it.

So do platform engineers in Salesforce-heavy orgs. Anyone trying to move from "senior dev" to "architect who signs off on designs" will get career mileage out of this Heroku Architect certification, which is the thing. You need that credential when you're influencing technical decisions at a level where wrong calls create expensive problems downstream.

Exam registration fee

For 2026, the Salesforce Heroku-Architect exam follows the standard architect-level pricing. The primary attempt? $400 USD. That's the number you plan around.

Price is intended to be consistent globally, but your local checkout can look a little different because currency conversion is a thing, and sometimes taxes or card processing quirks show up depending on region. The fee includes one complete attempt with official proctoring. That's it. No bundled Heroku Architect practice test, no included course voucher, no "free" question bank tossed in at checkout.

Payment's straightforward.

Credit card works. Debit card usually works. Approved corporate accounts can pay too, which matters if your employer's sponsoring you and wants the charge to land in the right place. Registration gets processed through Salesforce's Webassessor platform, and if you've taken any Salesforce cert before, you already know the vibe. A little clunky. Functional. Very "enterprise".

Invoice options exist for corporate-sponsored candidates. If you're at a partner or a big company, do the invoice route because expense reports get weird when you personally pay and then try to get reimbursed across borders and cost centers.

One sentence warning. No refunds once the exam's scheduled. Rescheduling's permitted, but you can't treat scheduling like a casual placeholder. Group discounts aren't typically offered for individual certifications, so don't expect "buy 3 get 1 free" unless you're in some separate training contract situation.

Pricing can change.

Salesforce does that. Verify the current rate on the official Salesforce certification site before you commit.

Retake fees and other costs (training, practice tests)

Retakes are where budgets quietly bleed. The first retake costs $200 USD, which is 50% of the original fee, and the second and every retake after that's also $200 USD each. Same price every time. No mercy discount if you missed by one question.

There's a mandatory 14-day waiting period between failed attempts, enforced through Webassessor. No limit on total attempts permitted, but each retake requires a brand-new registration and payment, and the retake fee applies regardless of your prior score. Failed attempts remain on your certification transcript permanently, which isn't the end of the world, but it's a reason to prep like you care.

Now the bigger cost usually isn't the exam fee.

It's prep.

Official Salesforce instructor-led training can run $3,000 to $5,000 USD. Self-paced online courses and video training are more like $200 to $800. The Heroku Architecture Designer certification exam itself's often treated as a prerequisite step and costs $200 USD, so if you're not already holding it, add that to your "real" Heroku certification cost.

Practice exams and question banks are usually $50 to $150 per resource. Some are decent. Some are trash. Study guides and reference books: $40 to $100. Hands-on lab environments and sandbox costs can be $0 to $500 monthly, depending on what you're building and whether you need paid add-ons. And if you're doing real practice projects on Heroku, expect $50 to $300 monthly for platform usage, especially if you're testing Postgres tiers, Redis, Private Spaces, or anything that looks like production.

Conferences? Optional, but useful. Budget $500 to $2,000. Coaching or paid study groups land around $100 to $1,000. Add it up and the total prep investment typically ranges $500 to $8,000, depending on whether you're doing scrappy self-study or going full corporate training plan.

I once knew someone who spent about three hundred bucks total on prep, passed first try, and then watched their coworker burn through two grand in courses and still need a retake. Sometimes you just need the right questions and a willingness to actually build things instead of watching someone else build them on video.

Passing score (what you need to pass)

People ask: What is the passing score for the Heroku Architect certification? Salesforce exams typically publish a passing score in the official exam guide for that credential, and it can change as the exam's updated. So the honest answer is: check the current Heroku Architect exam guide on the certification site for the exact number.

Don't treat the passing score like a target you can game.

The exam's designed so weak areas get exposed. Security and networking questions tend to do that.

Number of questions, time limit, and question types

The exact format details (question count, time limit, and scoring model) are also published in the official guide, and Salesforce can adjust them. Expect multiple choice and multiple select. Expect scenario questions where every option sounds "kinda right" but only one fits Heroku's recommended approach.

Time pressure's real.

Short questions exist. Many are long. Some are sneaky.

Delivery method (online proctored vs. test center)

You can usually take Salesforce exams online with proctoring or at a test center, depending on availability in your region and what Salesforce's offering at the time you register. Online proctored's convenient. It's also strict. Clear desk, stable internet, no wandering eyes, and yes, they can end your session if you violate rules.

Expected experience level (hands-on requirements)

People also ask: How hard is the Salesforce Heroku-Architect exam? Hard enough that memorizing docs won't save you. You need hands-on time with pipelines, Postgres, networking, and operational tooling. If you've never built a real Heroku CI/CD pipelines setup with review apps and promotion rules, the exam questions will feel like they're written in another dialect of English.

I'd say you want at least a year of real Heroku production exposure, or a shorter period if you're the type who builds labs and actually breaks things on purpose to learn the failure modes.

Tough domains (security, networking, data, operations)

Security's a classic trap.

Heroku security and compliance topics show up as design constraints, not trivia, and you've gotta know what's possible in Private Spaces versus Common Runtime, how to reason about inbound and outbound connectivity, and what "compliance" means in platform terms.

Data's another. Heroku Postgres high availability isn't "turn on a checkbox and forget it". The exam expects you to understand durability, HA/DR choices, follower databases, backups, and what architecture changes when the RPO/RTO expectations tighten.

Operations matters too.

Logging drains, metrics, alerting, incident response. The exam likes questions that test whether you'll build something operable by a team that isn't you.

Tips to reduce exam-day risk

Schedule when you're awake. Obvious, but people ignore it. Do at least one full timed practice run, even if you don't have an official Heroku Architect practice test, because pacing's half the game.

Another tip?

Write down your weak domains and fix them. Don't just rewatch videos.

Architecture and app design on Heroku (dynos, buildpacks, routing)

The Heroku Architect exam objectives will hammer core platform concepts. Dyno types and scaling patterns, buildpacks and slug compilation behavior, routing, request timeouts, and how to design for statelessness. If you still have a filesystem dependency mindset, you'll get punished.

Data layer (Heroku Postgres, caching, durability, HA/DR)

Know Postgres plans.

High availability patterns, maintenance windows, and how caching changes failure scenarios. Also, know what happens during follower promotion and how apps should behave when connections drop. That's real architecture.

Security, identity, and compliance

Expect identity patterns, key management approaches, config vars, least privilege thinking, and compliance-driven design choices. This is where "I read a blog post once" stops working.

Networking and runtime isolation (Private Spaces, VPC, connectivity)

This is the big brain section. Heroku Private Spaces architecture topics include VPC peering, private connectivity, DNS behavior, outbound controls, and what changes when you isolate runtime for governance reasons. It's where a lot of candidates either shine or sink.

Observability and operations (logging, metrics, incident response)

Logging drains.

Metrics sources, tracing concepts, and what you do when you need to debug a production issue without SSH-ing into a box because you can't. Heroku wants you thinking like an operator.

CI/CD and release management (pipelines, review apps)

Pipelines, review apps, promotions, release phase, rollback strategy. If you've done it for real, the questions feel fair. If you haven't, they feel petty.

Integration patterns (Salesforce plus Heroku, APIs, events)

This is where Salesforce integration with Heroku shows up. Auth flows, API-led patterns, event-driven integration, data sync considerations, and how to avoid building a fragile point-to-point mess that breaks every time Salesforce changes a permission set.

Required prerequisites (if any)

Salesforce may list prerequisites or recommended steps in the credential page.

The real practical prerequisite is competence. Not paperwork.

Recommended prior credentials (e.g., Heroku Architecture Designer)

A lot of people take the Heroku Architecture Designer certification first, and I agree with that sequencing. It's cheaper, it frames the platform concepts, and it reduces your risk of paying retake fees on the architect exam.

Skills checklist before attempting the exam

If you can't explain Private Spaces connectivity options, Postgres HA choices, a CI/CD pipeline design, and security controls without hand-waving, wait. Build a lab. Or ship a project. Then come back.

Official Salesforce resources (Trailhead, exam guide, docs)

Best place to start's the official exam guide plus Trailhead where it fits.

The guide tells you what Salesforce thinks matters. That's the test.

Heroku Dev Center and architecture documentation

Heroku Dev Center docs are where the real answers live, especially for operational behavior and limitations. Bookmark the Private Spaces docs. Read them twice.

Hands-on labs and reference architectures

Build something.

A small app's fine. Add Postgres. Add a pipeline. Add a logging drain. Then introduce failure scenarios. Break it. Fix it. That's how you learn the stuff the exam actually tests.

Study plan (2 to 6 weeks) by experience level

If you already run Heroku in production, 2 to 3 weeks of targeted study can be enough. If you're newer, 4 to 6 weeks is more realistic, because you need time for hands-on reps, not just reading Heroku Architect study materials.

Official practice test availability (and alternatives)

People ask: What are the best study materials and practice tests for Heroku Architect? Salesforce sometimes offers official practice exams for certain certs, sometimes not. If there isn't an official one, your alternatives are high-quality third-party question banks, internal company mock exams, and building your own mini quizzes from the exam objectives and docs.

What to look for in high-quality practice exams

Explanations matter more than scores.

If a practice resource can't explain why an answer's wrong, it's training you to guess, not to architect.

Watch for outdated content too. Heroku changes. Salesforce changes. Old questions can teach bad habits.

Mini quiz topics mapped to objectives

Try short sets on Postgres HA tradeoffs, Private Spaces connectivity choices, pipeline promotion rules, and security controls like config vars, secrets handling, and least privilege integration patterns.

Salesforce credential maintenance cycle (release updates)

People also ask: What are the prerequisites and renewal requirements for the Heroku Architect credential? Salesforce credentials typically require ongoing maintenance tied to product releases, usually via short online modules or assessments on Trailhead. Requirements and deadlines are posted on the credential maintenance pages, and they can change, so don't guess.

How to complete renewal modules and deadlines

Do them early.

Seriously. Put a calendar reminder in the first week the maintenance window opens, because missing it's an annoying way to lose active status.

What happens if you miss renewal

If you miss maintenance, your credential can move out of good standing until you complete the required steps, and that can matter if your employer or partner status depends on active cert counts.

Cost, passing score, and retake policy

How much does the Salesforce Certified Heroku Architect exam cost? $400 USD for the primary attempt in 2026 pricing guidance, with minor local currency variation. Retakes are $200 USD each, 14-day wait after a failed attempt, and no refunds once scheduled.

Passing score and exact exam format details live in the current official exam guide.

Check it before you book.

Difficulty and time to prepare

Hard if you're theory-only.

Fair if you've built systems with real constraints. Plan 2 to 6 weeks depending on experience, and budget for at least one retake even if your goal's to never need it.

Objectives, prerequisites, and renewal in one place

Use the official Heroku Architect exam guide for the objectives, confirm whether you should earn Heroku Architecture Designer certification first, and read the maintenance page so you don't get surprised later.

Cost-benefit analysis and ROI considerations

Money talk.

The ROI's usually the easiest part to justify.

Average salary increases often land around $8,000 to $15,000 annually for certified architects, and for consultants the billing rate premium can be $25 to $50/hour. That means the certification can pay for itself in 3 to 6 months through salary gains, sometimes faster if you switch jobs or move into a lead role. It also improves job mobility, can reduce time-to-hire, and gives you credibility when you're proposing architecture that touches compliance and platform risk, which is the stuff that slows deals down.

Employer reimbursement programs are common, sometimes covering 50% to 100% of costs, and some professional development expenses may be tax deductible depending on your country and situation.

Talk to a tax pro if you want certainty.

Long term, this is skills investment, because even as Heroku evolves, the core ideas around app design, data durability, networking isolation, and operations don't go out of style overnight.

Employer sponsorship and reimbursement strategies

Many Salesforce partners and consulting firms cover full certification costs. Ask. Don't be weird about it. Present a business case that connects the cert to better delivery, fewer production issues, and more credible client architecture recommendations, because leaders approve budgets when they can see risk reduction and revenue upside, not when they hear "I want a cert".

Negotiate certification budget as part of your annual development allowance, and get pre-approval before registering so reimbursement's clean. Document outcomes after you pass, like improved standards, better reference architectures, or faster project onboarding, because that makes the next budget request easier.

Training vouchers and bulk purchasing programs sometimes exist for teams, but don't count on public group discounts for this single certification.

If an employer sponsors you, they may ask for a retention agreement. Read it. Understand the payback clause. Then decide if it's still worth it, because being locked in for 18 months when you're underpaid is a raw deal no matter how shiny the cert looks on LinkedIn.

If you're job hunting, you can also use certification expectations in offers and negotiations. Some companies'll cover the exam cost as a signing perk, especially when they need Heroku architects and don't have enough on staff.

Passing Score, Exam Format, and Delivery Methods

Understanding what 60% actually means

The Salesforce Certified Heroku Architect exam requires a minimum passing score of 60%. Sounds simple enough. But Salesforce doesn't just count 36 out of 60 questions and call it done.

They use scaled scoring from 0-100%, which means they apply statistical equating to ensure fairness across different exam versions. This matters more than most people realize. If you take version A and I take version B, our 60% thresholds should represent the same level of competence even if the questions differ slightly in difficulty. Salesforce periodically reviews passing thresholds based on psychometric analysis. Fancy term for "we make sure the test is actually measuring what it should."

When you finish? You get your result immediately. Pass or fail. No "you got 59% so you almost made it" consolation prize. The system doesn't care if you missed by one question or ten. It's binary. What you DO get is a detailed score report breaking down your performance by exam objective domain, which is actually useful when you're staring at a failing score wondering what went wrong. Those domain breakdowns tell you exactly where to focus your retake prep.

No partial credit, no tricks

Every question on the Heroku-Architect exam is weighted equally.

A tough architecture scenario question about Private Spaces networking? Same weight as a question about buildpack behavior. This is both good and bad. You can't game the system by focusing only on "high-value" questions, but you also don't get punished extra hard for missing complex scenarios.

Multiple-choice questions don't award partial credit. If a question asks you to select three correct answers and you only pick two, you get zero points. Not 66%. Zero. Pretty standard for certification exams, but it's worth emphasizing because those multiple-select questions are where people often lose points thinking "well, I got most of it right."

The passing score stays consistent across all delivery methods too, which brings us to..

60 questions, 105 minutes, and the math you need to know

You get 60 multiple-choice and multiple-select questions with 105 minutes to complete them. That's 1 hour and 45 minutes, which breaks down to roughly 1.75 minutes per question on average. Sounds like plenty until you're staring at a scenario-based question with a code snippet and five plausible-sounding answers.

There are no scheduled breaks.

If you need to use the bathroom, the timer keeps running. If your proctor needs to verify something, timer keeps running. This isn't like some other Salesforce exams where you get explicit break time. You're on the clock the entire 105 minutes.

Here's my recommended pacing strategy: allocate 90 seconds per question with a 15-minute buffer at the end for review. This gives you time to flag tricky questions, move through the exam without panicking, and come back to review anything you marked. Some questions you'll answer in 30 seconds. Others will eat three minutes. The goal is averaging out to stay ahead of the clock.

The exam may include unscored survey questions, but here's the thing: they don't tell you which ones are surveys. You've gotta treat every question like it counts because it probably does. These survey questions help Salesforce develop future exam versions, but they don't affect your score and aren't included in the 60-question count.

What the questions actually look like

Most questions are standard multiple-choice with one correct answer. Pick A, B, C, or D. But you'll also see multiple-select questions requiring you to choose 2-3 correct answers from a list of options. The exam tells you how many to select ("Choose 3 answers" is typical phrasing) so at least you're not guessing how many are correct.

Scenario-based questions are where the Heroku-Architect exam shows its teeth. And I mean really shows them. You'll get a paragraph describing an architectural challenge: a company needs to integrate Heroku apps with Salesforce, maintain PCI compliance, handle 10,000 requests per second, ensure zero downtime deployments, and oh by the way their data can't leave the US. Now pick the best approach from five options that all sound kinda reasonable.

Some questions include code snippets (Procfile configurations, buildpack settings, or Heroku CLI commands), architecture diagrams showing dyno configurations or Private Spaces topology, or configuration examples for add-ons like Heroku Postgres. The distractors (wrong answers) are designed to test whether you actually understand how Heroku works or if you just memorized some Trailhead modules.

You won't find any essay questions or hands-on labs.

This is entirely objective multiple-choice testing. Which means you can't explain your reasoning or partially demonstrate knowledge. You either select the right answer(s) or you don't.

Online proctored: convenient but strict

Most people take the Heroku-Architect exam via online proctoring because it's just more convenient. Schedule an appointment, take it from home, done. But "convenient" doesn't mean "relaxed." You need a quiet, private space where you won't be interrupted for nearly two hours. Your significant other walking through the background? That could get your exam flagged.

Technical requirements are non-negotiable: webcam, microphone, stable internet, desktop or laptop computer. No tablets, no phones. Before the exam starts, you run a system check to verify everything works. Then a live proctor connects via webcam and monitors you the entire time.

The rules are strict.

No notes, no secondary monitors, no phones within reach, no reference materials. You'll do a room scan with your webcam showing the proctor your entire workspace: desk, walls, under the desk, everything. They're looking for notes taped to monitors, books within reach, anything that could be used for cheating. Scratch paper? Nope. Calculator? Prohibited (though the exam doesn't really require calculations).

If you have connection issues, technical support is available, but that's stressful when you're trying to maintain focus. The advantage is scheduling flexibility. Appointments are available 24/7 in most regions, so you can take the exam at 11 PM on a Tuesday if that's when you're most alert or when your brain just works better. I once took a different cert at 6 AM because I'm a morning person and figured fewer network issues at that hour, which turned out to be completely wrong since the proctoring service was apparently doing maintenance.

Test center: old school but reliable

Pearson VUE test centers offer in-person delivery for people who prefer a controlled environment or have unreliable home internet. You show up, they verify your identity, you put your belongings in a locker, and they seat you at a standardized computer workstation.

The test center provides everything: computer, desk, sometimes scratch paper (policies vary). Proctors are physically present if you have questions or technical issues. There's something to be said for eliminating the home environment variables. No worrying about your internet dropping or your neighbor deciding to mow the lawn during your exam.

Downsides?

You've gotta travel to the center, which might be inconvenient depending on where you live. Appointment availability is more limited compared to online proctoring. And you're still taking the exact same exam with the same time limit and question format, so it's really just about personal preference and circumstances.

What happens on exam day

Whether online or in-person, arrive (or log in) 15 minutes early for check-in. You'll need a government-issued photo ID. Driver's license, passport, something official with your photo and the name matching your exam registration.

Before accessing the exam, you sign an NDA agreeing not to share exam content. Then you're in. 105 minutes starts immediately. No bathroom breaks without the clock running. No pausing to look something up. Just you, 60 questions, and the timer counting down.

Questions appear one at a time.

You can flag questions for review and work through back to them before submitting. Most people flag 10-15 questions on their first pass, then use remaining time to review those carefully. The exam shows a timer throughout so you always know how much time is left.

When you submit, you get your result immediately. Pass or fail displayed on screen. If you passed, congrats. Your official certificate gets issued within 1-2 weeks. If you failed, the score report shows which domains need work before your retake.

Violating exam policies (having unauthorized materials, trying to screenshot questions, getting help from someone) results in exam invalidation and potentially being banned from future Salesforce certifications. Not worth it.

Rescheduling and retake logistics

Need to reschedule?

You can do it up to 24 hours before your appointment, though Salesforce may charge a rescheduling fee. Cancel within 24 hours and you forfeit the entire exam fee (currently $400 for the Heroku-Architect). Retakes cost the same as the original exam, so failing gets expensive quickly.

This is where quality prep materials matter. The Heroku-Architect Practice Exam Questions Pack helps you identify weak areas before dropping $400 on the real thing. At $36.99, it's a pretty cheap insurance policy against having to pay for multiple retake attempts. I've seen people take the exam three or four times because they didn't prep properly. That's $1,600+ in exam fees alone.

If you're coming from other Salesforce certifications like Integration-Architect or Identity-and-Access-Management-Architect, you already know how Salesforce structures their architect-level exams, but the Heroku-Architect follows similar patterns while testing different knowledge domains. Even experienced architects need to study Heroku-specific concepts like dyno management, buildpack behavior, and Private Spaces networking. Stuff that doesn't overlap much with platform-focused certs like Platform-App-Builder.

The psychological game

Seeing that timer count down while you're wrestling with a complex architecture scenario creates pressure. Some people thrive on it. Others freeze. Know which type you are and practice accordingly.

The immediate pass/fail result is both blessing and curse. Pass and you get instant gratification, fail and you're sitting there feeling pretty lousy while the result screen stares at you. Either way, you know immediately whether those weeks of study paid off.

Difficulty Level: How Hard Is the Salesforce Heroku Architect Exam?

What this credential really proves

The Salesforce Certified Heroku Architect credential is basically Salesforce saying: you can design, secure, deploy, and run serious Heroku systems without guessing. Not toy apps. Not "I pushed a build once."

It's architecture plus operations. The ops part is what trips up a lot of otherwise strong developers. Like, developers who can write beautiful code but freeze when someone asks about connection pool saturation at 2 AM.

Who should even take it

Look, if you've mostly lived in Salesforce admin land, this exam is gonna feel like you walked into an SRE interview by accident. If you've been building Heroku apps for real, with pipelines, data services, networking, and incident cleanups, it's very doable.

You should be the person people call when a production dyno is thrashing. Postgres connections spike. And the business still wants a "no downtime deploy" today. That person.

How much the Heroku Architect certification cost will run you

The Heroku certification cost is the exam fee Salesforce sets, plus whatever you spend prepping.

Exam registration fee varies by region, but plan for the typical Salesforce credential pricing tier. Retakes cost extra. Training can add up fast if you buy instructor-led stuff.

Also, practice resources. If you want something targeted, I'll mention the Heroku-Architect Practice Exam Questions Pack ($36.99) because getting used to the question style matters more than people admit.

Retake fees and the "hidden" costs

Retakes are the obvious one. The sneaky cost? Time.

You lose weekends. You spin up test apps. You pay for dynos, Postgres tiers, maybe Private Spaces if your employer isn't footing the bill. Add a little buffer for that.

I once knew a developer who spun up a Private Space just to test network peering for four hours, forgot to tear it down for a week, and got a bill that made him reconsider his entire study approach. That's the kind of thing nobody warns you about until it happens.

What passing looks like and how the test behaves

Salesforce exams usually tell you the passing score in the official listing, and it can change, so I'm not gonna pretend a random number I type here is gospel. Check the official listing the week you schedule.

Question count and time limit follow the standard Salesforce format. Multiple choice, multiple select. Scenario heavy. You'll see "best answer" style prompts where two options feel plausible, and the difference is some Heroku-specific detail that only clicks if you've actually built the thing.

Online proctored or test center. Either way, time management is real. A few long scenario questions can eat minutes like nothing.

Why the Salesforce Heroku-Architect exam feels hard

This Salesforce Heroku-Architect exam isn't hard because of trick questions. It's hard because it expects lived experience.

Salesforce recommends 3 to 5 years of hands-on Heroku platform work. That's not marketing fluff. You're expected to have architected and deployed at least 5 to 10 production Heroku applications, and not all identical clones either, because the exam hits variety. Different data needs. Different scaling patterns. Different integration approaches.

Three short truths. You can't fake networking. You can't cram ops.

Candidates without enough hands-on time typically struggle, because the exam keeps asking about trade-offs that only make sense when you've been burned before. Like when you chose the "simple" option and then spent a week untangling it in production while your manager asked increasingly pointed questions about timelines.

The hands-on requirements people underestimate

You need experience managing apps across dev, staging, and production environments. Pipelines. Promotion workflows. Config vars discipline. Release coordination with stakeholders who don't care about your deployment window.

Practical knowledge of Heroku Postgres, Redis, and other data services is expected. Not "I know what Redis is." More like you've tuned connection pools, decided when to cache, and understood what happens when you add followers or push a database upgrade.

Real-world exposure to Heroku Private Spaces architecture, networking, and security configs is also a big deal. VPC peering, internal routing, inbound and outbound controls, IP whitelisting, connectivity patterns. If those words feel abstract, you're early.

You should also have implemented Heroku CI/CD pipelines and release management workflows. Review apps. Automated tests. Buildpack behavior. Rollback thinking. And yeah, familiarity with Heroku CLI, API, and programmatic management tools is expected because architects don't click everything manually forever.

Difficulty compared to other Salesforce certifications

It's generally more difficult than Salesforce Administrator certs. That's not a diss, it's just a totally different skill stack.

Difficulty-wise, it's comparable to other architect-level credentials like Application Architect and Integration Architect, but it's more specialized. It also requires deeper technical knowledge than the Heroku Architecture Designer certification, which is why doing that one first can be a smart ramp if you're not already living in Heroku every day.

It's less conceptual than some architect exams. More implementation-focused. More "what would you actually do Monday morning" than "what is a pattern called."

Passing rates are usually estimated around 55 to 65%. Lower than associate-level certs. Higher than you'd fear if you truly have the background.

The domains that punch people in the face

Security and compliance architecture is a monster topic. Heroku security and compliance means you need to think encryption at rest and in transit, certificate management, SSO implementation, and how compliance frameworks affect architecture choices. Not gonna lie, this part is where a lot of pure app devs realize they've been relying on someone else.

Private Spaces networking is its own exam inside the exam. VPC peering, internal routing, IP whitelisting, connectivity patterns to Salesforce and to on-prem. One wrong assumption about where traffic flows and you pick the wrong answer.

High availability and disaster recovery matters more than people think. You need to know Heroku Postgres high availability concepts like HA configs, followers, point-in-time recovery, and what failover strategy even means when your app tier scales independently but your database doesn't.

Performance optimization is another sinkhole. Dyno sizing. Horizontal scaling. Connection pooling. Caching strategies. CDN integration. Lots of "it depends," but the exam wants the best default choice for a given constraint.

Salesforce integration patterns add extra complexity because you're doing cross-platform design. Choosing between Heroku Connect, APIs, webhooks, and event-driven designs isn't theoretical. You're balancing latency, consistency, rate limits, data volume, and operational complexity in one go. One wrong choice can cascade through your entire architecture.

The rest show up too, just more quietly: observability and monitoring, cost optimization, build and release engineering, multi-region and global deployment with data sync.

Common reasons people fail

Insufficient hands-on Heroku feature exposure is the big one. Second is relying on theoretical knowledge and thinking that reading docs equals knowing.

Other common misses are not understanding the small differences between similar approaches, weak networking fundamentals for Private Spaces, limited Postgres HA experience. People underestimate the technical depth because "it's a Salesforce cert so it'll be friendly." It's friendly. It's still hard.

Preparation time is another. Less than 40 to 60 hours of focused study tends to be thin unless you already do this work daily.

Also, exam-day stuff. Poor time management leads to unanswered questions. And people skip the official Heroku Architect exam guide and Heroku Architect exam objectives, which is wild to me because Salesforce literally tells you what they care about.

Realistic prep time, based on where you're at

Expert Heroku users (5+ years): 40 to 60 hours over 3 to 4 weeks, mainly closing gaps and doing targeted review.

Experienced Heroku developers (3 to 5 years): 80 to 100 hours over 6 to 8 weeks with a full sweep of objectives.

Intermediate (1 to 3 years): 120 to 150 hours over 10 to 12 weeks, with hands-on labs baked in.

Salesforce architects new to Heroku: 150 to 200 hours over 12 to 16 weeks, because you're learning platform behavior, not just memorizing terms.

Developers with limited Heroku exposure should get more real experience first. Seriously. Otherwise you're paying to be stressed.

Hands-on lab work should be 40 to 50% of your prep. Consistent daily study beats cramming. Quality matters more than raw hours, but you still need the hours.

Ways to make the exam feel less brutal

Do the Heroku Architecture Designer certification first if you need a structured foundation. Build and deploy multiple reference architectures covering different patterns, not just one stack with different names.

Focus heavily on the official exam guide and objectives. Then read Heroku Dev Center docs systematically, not randomly.

Take practice exams to find weak spots and improve timing. If you want something quick to pressure-test your readiness, the Heroku-Architect Practice Exam Questions Pack is a decent option to rehearse the style and spot where you're guessing. Review your misses. Write down why.

Study groups help if they're serious. Document your labs. Create your own reference architecture repo with notes like "why I chose this" and "what breaks first."

Practice saying trade-offs out loud. Sounds silly. Works though.

Schedule the exam when you're ready, not when you're tired of studying. Sleep the night before. Boring advice. Still matters.

Prereqs and what you should already be able to do

No hard prerequisite credential is required, but the practical prerequisites are real.

You should be comfortable with dynos, buildpacks, routing basics, add-ons, config vars, and Heroku pipelines. You should be able to design data layers with Postgres and caching, and explain backup and recovery choices. You should know security basics, identity patterns, and how Private Spaces change networking.

And you should have real Salesforce integration with Heroku experience. Auth flows. Data sync choices. Eventing where it makes sense.

Study materials that actually help

Official Salesforce resources: Trailhead, the exam guide, and the objective breakdown. Heroku Dev Center is non-negotiable. Architecture docs too.

Hands-on labs matter. Build a small system with a web app, worker dynos, Postgres, Redis, a pipeline with review apps, logging and metrics, and at least one Salesforce integration path. Break it on purpose. Fix it.

If you want a timed drill, grab the Heroku-Architect Practice Exam Questions Pack and treat it like a diagnostic, not a confidence booster.

Practice tests and what "good" looks like

A good Heroku Architect practice test is scenario-driven, explains why wrong answers are wrong, and maps back to objectives. If it's just trivia, it won't help.

Mini quiz topics you should be able to answer cold: Private Spaces routing decisions, Postgres follower and PITR behavior, dyno scaling versus connection pooling, Heroku Connect versus API-led integration, and what you monitor first during an incident.

Renewal and maintenance stuff

Salesforce credentials usually have periodic maintenance modules tied to releases. Deadlines matter. If you miss renewal, your credential can lapse and you're back to fixing paperwork instead of building systems.

Check the maintenance page after you pass. Put reminders on your calendar. Future you will be grateful.

FAQs people keep asking

How much does the Salesforce Certified Heroku Architect exam cost? It's the exam fee plus retakes and whatever you spend on training or practice resources, so budget beyond the sticker price.

What is the passing score? Salesforce publishes it on the official exam page, and that's the only source I trust.

How hard is the Salesforce Heroku-Architect exam? Hard if you're light on real Heroku ops and networking, very manageable if you've shipped and supported multiple production apps.

Best study materials? Official docs, hands-on builds, and a solid set of practice questions. The exam guide and objectives are your checklist.

Prerequisites and renewal? No required prereq cert, but you need serious hands-on experience, and you'll have ongoing maintenance modules to keep it current.

Heroku Architect Exam Objectives: Full Domain Breakdown

I've worked with Salesforce certifications for years now, and honestly the Heroku Architect path is one of the most underrated credentials in the ecosystem. Not gonna lie, when people think Salesforce they usually picture CRM and maybe some Platform App Builder stuff, but the Salesforce Certified Heroku Architect exam tests something completely different: you're proving you can design cloud-native applications that scale, integrate with core Salesforce products, and handle real production workloads without falling apart under pressure.

The thing is, the Heroku Architect certification isn't just another checkbox. It validates that you understand how to architect solutions on a platform-as-a-service that thousands of companies rely on for everything from microservices to full-stack web apps. If you're already certified in areas like Integration-Architect or Identity-and-Access-Management-Architect, adding Heroku Architecture expertise makes you way more valuable for hybrid cloud projects. I mean, companies are literally desperate for people who can bridge both worlds right now.

Breaking down the core exam domains

The Salesforce Heroku-Architect exam divides content into several weighted domains, and you need to know them cold. Really know them. Not just memorize flashcards the night before and hope for partial credit.

Architecture and Application Design on Heroku makes up 18-22% of the exam, which is substantial. This section hammers you on dyno types: Standard, Performance, and Private. You need to know when you'd actually use each one in production environments versus development sandboxes. Standard dynos? Fine for dev work or low-traffic apps that don't need guaranteed uptime. Performance dynos give you more memory and better processing power when you're dealing with compute-intensive tasks or need consistent performance SLAs that won't embarrass you in front of stakeholders. Private dynos run in Private Spaces with network isolation, which is huge for compliance scenarios where regulators actually check your architecture diagrams.

You also need to design horizontally scalable applications. Stateless architecture is non-negotiable here. If your app stores session data locally on a dyno, you're gonna have a bad time when Heroku cycles that dyno or you scale to multiple instances and users suddenly get logged out randomly. The exam will absolutely test whether you know how to externalize state using Redis, Postgres, or other backing services.

Buildpacks come up too. Selecting and configuring the right buildpack (whether it's the official Ruby, Node.js, Python, or Java buildpacks, or custom ones) determines how your code gets compiled and what dependencies get installed during the build phase before anything even runs.

Data architecture gets deep fast

Heroku Postgres high availability and disaster recovery scenarios form a critical chunk of the data domain that separates people who've actually architected systems from those who just read blog posts. You're expected to know about follower databases for read scaling, continuous protection with point-in-time recovery, and how Premium and higher tier databases offer HA features like automatic failover that kick in when things go sideways. I've seen candidates stumble on questions about RPO and RTO requirements because they didn't actually work through real DR planning exercises where business stakeholders ask uncomfortable questions about data loss tolerances.

Caching strategies matter here. When should you use Heroku Redis versus relying on Postgres query optimization? How do you implement cache invalidation patterns that don't leave stale data sitting around for hours confusing users and generating support tickets?

The exam wants proof you've thought about durability versus performance tradeoffs in real architectures. Not theoretical ones.

Security and compliance can't be an afterthought

The security domain covers Heroku security and compliance requirements that go way beyond "just use HTTPS and call it a day." You need to understand Private Spaces networking, VPC peering to AWS resources, mutual TLS for app-to-app communication, and how to implement proper identity and access management using OAuth, SAML, or Salesforce Identity integration without creating security holes attackers could drive trucks through.

Compliance frameworks like SOC 2, ISO 27001, and HIPAA eligibility come into play when you're working with regulated data. Healthcare, financial services, that sort of thing. The exam tests whether you know which Heroku features support these frameworks and what architectural patterns you need to follow to pass audits. For instance, Private Spaces with Shield add-ons give you encryption at rest and enhanced audit logging that standard Heroku apps don't provide, which auditors love seeing in documentation.

Networking and runtime isolation separate good architects from great ones

This is where Heroku Private Spaces architecture knowledge becomes essential. No exaggeration. Private Spaces create network-isolated environments within AWS regions, giving you dedicated runtime and routing infrastructure that doesn't share resources with random other Heroku customers. You configure Internal Routing for apps that shouldn't be internet-accessible, set up Trusted IP Ranges to control inbound traffic, and establish Private Space VPN or Peering connections to corporate networks or other cloud resources.

Understanding the routing layer matters. How Heroku's HTTP routers distribute requests across dyno instances, handle SSL termination, and implement connection pooling: these details are key when you're diagnosing production issues at 2 AM. I've worked with teams who didn't grasp that the router can time out connections if your app takes too long to respond. This leads to mysterious 503 errors under load that disappear when traffic drops.

On a related note, I once spent three hours troubleshooting what turned out to be a client's firewall rule that was randomly blocking specific AWS IP ranges where their Private Space ran. Sometimes the most "sophisticated" architectural problems have stupidly simple causes that make you question your career choices.

Observability keeps production systems running

The operations domain tests your knowledge of logging, metrics, and incident response. Basically everything that keeps you employed when systems inevitably have problems. Heroku's log drains let you ship logs to services like Splunk, Datadog, or Papertrail, but you need to architect log aggregation that handles high volume without dropping messages during traffic spikes. Heroku CI/CD pipelines integrate monitoring and alerting into the deployment workflow so you catch problems before they hit production and executives start asking pointed questions about your architectural decisions.

Application Performance Monitoring integration with tools like New Relic helps you identify bottlenecks. Database queries taking forever? External API calls timing out? Inefficient code paths burning CPU cycles? The exam expects you to know how to interpret metrics like dyno load averages, memory usage patterns, and request queue depth to make intelligent scaling decisions rather than just throwing more resources at problems randomly.

CI/CD and release management practices

Review apps, pipelines, and promotion workflows form the foundation of modern Heroku CI/CD pipelines that don't make developers want to quit. You should know how to configure Heroku Pipelines with development, staging, and production stages. Use Review Apps to spin up temporary environments for each pull request (which is incredibly useful for code reviews). Implement safe promotion strategies that include rollback capabilities for when deployments inevitably go wrong despite everyone's best efforts.

The exam covers release phase scripts that run during deployment: database migrations, cache warming, feature flag updates. Understanding when these scripts run and how failures affect deployment is important. If your migration fails during release, does Heroku roll back the entire deployment or just halt it? The answer affects your deployment strategy and rollback procedures.

Integration patterns connect everything

Salesforce integration with Heroku represents a major portion of the exam since that's literally the whole point of having Heroku in the Salesforce ecosystem. You need to know Heroku Connect for bidirectional data sync between Postgres and Salesforce objects. Using Salesforce APIs from Heroku apps with OAuth flows that don't expose credentials. Event-driven architectures using Platform Events or Change Data Capture for near-real-time integration patterns.

API design patterns matter too. RESTful versus GraphQL, synchronous request-response versus asynchronous message queuing, webhook handling with retry logic: these architectural decisions directly impact reliability and user experience in ways that show up in production metrics. Similar to how Certified-Marketing-Cloud-Consultant candidates need to understand integration across marketing channels, Heroku architects must design integration patterns that work across multiple systems without creating fragile dependencies that break constantly.

What the exam actually costs and how to prepare

The Heroku certification cost runs $400 for the initial attempt, same as most Salesforce architect-level credentials, which adds up fast if you're collecting multiple certifications. Retakes cost $200 if you don't pass the first time, so you want to prepare thoroughly and not just wing it hoping your general cloud experience carries you through. Budget another $200-500 for quality Heroku Architect study materials like hands-on lab subscriptions or third-party courses if you're not already deep in Heroku daily building actual production systems.

The exam is challenging. You need real hands-on experience building and operating Heroku applications, not just theoretical knowledge from documentation. If you're coming from a traditional Salesforce admin background like ADM-201 or Certified-Platform-App-Builder, expect a learning curve around cloud-native architecture patterns and DevOps practices that might feel uncomfortable at first.

Practice tests and study approach

Quality Heroku Architect practice test resources are harder to find than for core Salesforce certs, unfortunately. The community just isn't as large yet. But the official Salesforce exam guide provides sample questions and a practice exam that give you a sense of question style and difficulty. I always tell people to build actual projects in Heroku: deploy apps using different buildpacks, configure Private Spaces, set up Heroku Connect with a Developer Edition org, implement logging pipelines that actually ship data somewhere useful.

The Heroku Dev Center documentation? Your bible. Read the architecture articles. Review the reference implementations. Understand the twelve-factor app methodology since Heroku's design philosophy follows it closely and exam questions assume you know those principles.

Renewal happens through Salesforce's maintenance exam cycle. You'll complete modules covering new features and platform updates each release, typically three times per year. Miss your deadline and the credential expires, requiring you to retake the full exam and pay another $400.

This certification opens doors. Roles designing sophisticated cloud architectures that span Salesforce CRM and custom applications pay well and offer interesting technical challenges. It's worth the effort if you're serious about becoming a complete Salesforce ecosystem architect rather than just specializing in one narrow area.

Conclusion

Wrapping up your Heroku Architect path

Okay, real talk here.

The Salesforce Certified Heroku Architect credential isn't something you'll knock out during a lazy weekend. The exam objectives alone throw everything at you from Heroku Postgres high availability and Private Spaces architecture all the way through CI/CD pipelines and those tricky cross-cloud integration patterns with Salesforce. You've gotta log real hands-on hours with dynos, buildpacks, and networking configs before even thinking about scheduling this beast.

The Heroku certification cost? About $400 first attempt. Steep? Sure feels like it initially, but once you see what doors this thing opens career-wise, that price tag makes sense. Most architects I've chatted with who actually passed spent somewhere around 4-6 weeks prepping, though that timeline assumes you've already wrestled with Heroku in production environments. Coming from pure Salesforce background without much platform-as-a-service experience? Tack on another month minimum. Maybe two if we're being honest.

What's brutal? The breadth.

You can't just dominate application design while fumbling through security and compliance. The exam'll absolutely grill you on Private Spaces networking, observability tooling, data durability strategies. All of it. Not gonna sugarcoat it: those sections covering integration patterns between Salesforce and Heroku wreck people constantly since you've gotta know both ecosystems inside-out.

Your study plan should lean heavily on the official Heroku Architect exam guide plus Dev Center documentation, but here's the thing. Just reading architecture docs only carries you so far. You've gotta actually build reference architectures. Deploy apps, break things (intentionally), configure Postgres followers, test failover scenarios yourself.

What nobody mentions: the Heroku Architect practice test options floating around vary wildly in quality. Some're just keyword dumps teaching you nothing about actual architectural decision-making. You want practice questions mirroring that scenario-based format the real exam uses, where they hand you a business requirement and you've gotta recommend the right Heroku services, security controls, integration approach.

Actually, speaking of integration approaches, I once spent three days debugging a Heroku Connect sync issue that turned out to be a field-level security setting in Salesforce. Three days. Could've been thirty minutes if I'd checked permissions first, but you live and learn.

Before scheduling your Salesforce Heroku-Architect exam, make absolutely certain you're testing yourself under realistic conditions. The Heroku-Architect Practice Exam Questions Pack at /salesforce-dumps/heroku-architect/ delivers that scenario-based practice with detailed explanations for every answer, which matters way more than just knowing if you got it right or wrong.

Study smart. Build real stuff. You'll pass.

Show less info