UUS Practice Tests⌕ Search
IT Certifications · Plat-Arch-206

Salesforce Heroku Arch Exam Practice Test

Heroku architecture work centers on designing and operating applications on the Heroku platform. Relevant skills include choosing add-ons for external services, defining process types, managing deployments, and diagnosing runtime behavior across dynos. The practice material also touches on request handling, application readiness, memory use, and data-processing patterns.

Exam overview

Exam providerSalesforce
Exam codePlat-Arch-206
CategoryIT Certifications

About the Salesforce Heroku Arch Exam

Architects need to connect application design with Heroku’s operational model. This includes deciding how web and background processes should be separated, how a Procfile communicates process types, and how repository-based deployment can fit into build, test, and release workflows. Operational decisions include gathering logs and runtime evidence to investigate errors or memory pressure, and tracing requests across related application events. Application design also involves handling external callbacks, integrating services such as email through add-ons, and avoiding unsafe in-memory processing for large datasets. Shared reference data raises questions about how multiple dynos access consistent information. These concepts support practical tradeoffs among reliability, scalability, maintainability, and access control when building and running Heroku applications.

Sample Practice Questions

Review a selection from this exam's published US Practice Tests practice bank.

Question 1

A Heroku app needs to send outbound email through a third-party provider. Which approach best fits Heroku's add-on model?

  1. AInstall the provider's mail server on every dyno
  2. BUse a compatible email add-on or external service and configure the app to use its supplied settings
  3. CStore outgoing messages in the app slug and send them during each build
  4. DUse the Heroku router as an SMTP relay
Show answerCorrect answer: B

Heroku add-ons and external services can provide capabilities such as email delivery. The app is configured to use the service's connection details or credentials rather than hosting mail infrastructure on its dynos.

Question 2

A team wants a Heroku app to receive traffic only after its process has initialized required local resources. Which configuration is most relevant to controlling the app's startup readiness?

  1. AA health check that reports readiness after initialization
  2. BA scheduled job that restarts the app at regular intervals
  3. CA larger dyno size so startup takes less time
  4. DA second Procfile entry for the same web process
Show answerCorrect answer: A

A readiness health check can indicate whether an instance is prepared to serve requests, allowing traffic management to account for startup state. It should reflect actual readiness rather than merely whether the process exists.

Question 3

A team wants to automate build, test, and release steps when code changes are pushed to a repository. Which Heroku capability can connect an app to a source repository and support automatic deploys?

  1. AHeroku GitHub integration
  2. BHeroku Postgres data clips
  3. CA custom domain
  4. DDyno metadata
Show answerCorrect answer: A

Heroku's GitHub integration can connect an application to a GitHub repository and support automated deployment workflows, including deploys triggered by changes to a selected branch.

Question 4

A team is investigating whether a Heroku app is running out of memory. Which evidence is most useful to collect first?

  1. AThe application's memory-related runtime metrics and relevant process logs over the affected period
  2. BThe number of files in the team's source repository
  3. CThe custom domain's DNS record history alone
  4. DThe buildpack's display name
Show answerCorrect answer: A

Runtime resource metrics can show memory consumption and related events, while logs provide context about application behavior and restarts. Together they help identify whether memory pressure is occurring and when.

Question 5

A Heroku app needs to process a large data set that does not fit safely into one in-memory operation. Which implementation approach is generally preferable?

  1. AProcess the data in bounded batches and persist progress
  2. BLoad the entire data set into memory in every web request
  3. CIncrease the HTTP response body until processing finishes
  4. DRestart all dynos whenever a batch completes
Show answerCorrect answer: A

Bounded batch processing limits memory use and makes long-running work easier to monitor and resume. Persisting progress or checkpoints can support safe recovery if a process stops before completing the full data set.

Question 6

A team wants an application to receive events from an external provider through a callback URL. Which application capability is needed?

  1. AAn HTTP endpoint reachable by the provider
  2. BA one-off dyno that remains open indefinitely
  3. CA release created for each individual event
  4. DA private database connection string exposed to the provider
Show answerCorrect answer: A

External callbacks, commonly called webhooks, are delivered to an HTTP endpoint that the provider can reach. The endpoint should validate incoming requests and handle retries or duplicate delivery safely.

Question 7

A Heroku app's source code is stored in a Git repository. What is a useful reason to keep a Procfile in the project?

  1. AIt declares process types and the commands used to start them
  2. BIt stores encrypted database backups
  3. CIt defines custom DNS records for the app
  4. DIt selects the region for each individual request
Show answerCorrect answer: A

A Procfile can explicitly declare process types, such as a web process, and the commands Heroku should run for them. It does not manage backups, DNS, or request routing regions.

How to use this practice test

The free practice bank contains 50 questions; each session presents up to 20 random questions. Use a session to test your reasoning about Heroku deployment, process configuration, add-on integration, and runtime troubleshooting. Results appear after the session, helping you identify topics to revisit.

Preparation tips

  • Review how Procfile process types relate to web and background workloads, and consider when separating processes improves resource control.
  • Practice diagnosing memory pressure and intermittent errors by identifying useful runtime evidence, log context, and request-correlation information.
  • Compare approaches for processing datasets that exceed safe in-memory limits, including chunking or background work where appropriate.
  • Think through how add-ons, callback endpoints, and source-repository deployment fit into an application's integration and release workflow.
  • Evaluate how team access controls and shared reference data affect the security and operation of a multi-dyno application.
Official sourceOfficial exam page ↗