We're so confident of our products that we provide no hassle product exchange.
Salesforce Plat-Arch-206 Exam Overview:
| Certification Vendor: | Salesforce |
| Exam Name: | Salesforce Certified Heroku Architect |
| Exam Number: | Plat-Arch-206 |
| Certificate Validity Period: | 3 years (maintenance required) |
| Available Languages: | English |
| Passing Score: | 70% |
| Related Certifications: | Salesforce Certified Platform Developer I Salesforce Certified Platform Developer II Salesforce Certified Data Architecture and Management Designer |
| Exam Duration: | 105 minutes |
| Exam Format: | Multiple-choice, Multiple-select |
| Exam Price: | $400 USD |
| Real Exam Qty: | 60 |
| Sample Questions: | Salesforce Plat-Arch-206 Sample Questions |
| Exam Way: | Online proctored or at a testing center (via Kryterion) |
| Pre Condition: | No formal prerequisites. Salesforce recommends practical experience with Heroku and Salesforce platform integrations. |
| Official Syllabus URL: | https://trailhead.salesforce.com/en/credentials/herokuarchitect |
Salesforce Plat-Arch-206 Exam Syllabus Topics:
| Section | Objectives |
|---|---|
| Topic 1: Heroku Enterprise | - Heroku Enterprise architecture and Private Spaces - Heroku External Objects and Connect REST APIs - Heroku Connect and Salesforce-to-Heroku data synchronization - Heroku Enterprise account management and governance - Private Space peering and VPN connections - Regional deployment and data residency requirements |
| Topic 2: Integrations | - Messaging and event-driven architecture (Kafka, Redis Pub/Sub) - Heroku Button and deploy-to-Heroku workflows - Heroku Connect bidirectional sync with Salesforce CRM - Third-party service integration patterns (SaaS, APIs, webhooks) - Integration with Salesforce Platform Events and Change Data Capture |
| Topic 3: Data | - Database migrations and schema management - Heroku Postgres architecture, plans, and provisioning - Heroku Redis architecture and use cases - Data replication and high availability strategies - Apache Kafka on Heroku architecture and use cases - Heroku Postgres administration (backups, forks, followers, data clips) |
| Topic 4: Architecture and Application Design | - 12-factor app methodology and best practices on Heroku - Microservices and service decomposition on Heroku - Performance tuning and scalability (autoscaling, dyno sizing) - Continuous integration and continuous delivery (CI/CD) pipelines - Worker processes, background jobs, and queue processing (Heroku Redis, Apache Kafka) - API-first design and Heroku as a back-end for mobile/IoT apps |
| Topic 5: Security | - TLS/SSL and certificate management - Compliance and security best practices (SOC 2, GDPR) - Trusted IP ranges and firewall rules - Heroku Shield and HIPAA-compliant architectures - Private Spaces and network isolation - Identity and access management (SSO, Heroku Teams permissions) |
| Topic 6: Heroku Platform | - App lifecycle management (releases, rollbacks, preboot) - Heroku runtime and slug management - Heroku CLI and deployment workflows (git push, GitHub integration) - Logging, monitoring, and alerting (Logplex, Heroku metrics, third-party add-ons) - Heroku architecture and components (dynos, dyno formation, process types) - Configuration management (environment variables, config vars) - Add-ons ecosystem and marketplace - Heroku Teams and enterprise account management |
Salesforce Certified Heroku Architect Sample Questions:
1. A client has a Heroku Postgres database add-on attached to a production application. The client now wants to access the database from another application that they use to perform administrative tasks. What should an Architect recommend in this scenario?
A) Attach the same Heroku Postgres add-on to the administrative application
B) Create a fork of the database and attach it to the administrative application.
C) Attach the database toan application that acts as a database proxy
D) Copy the database's connection URL and add it to the administrative application as a config var.
2. Universal Containers needs to write their Heroku application's logs to twodestinations: an on-premise Syslog log server and a cloud analytics provider that ingests logs using an HTTPS endpoint.
What should an Architect recommend in this scenario?
A) Write all logs to stdout, and configure a separate log drain for each destination.
B) Publish all logs to Apache Kafka on Heroku, and create a separate app thatconsumes and distributes log messages.
C) Add a logging library to the application source that sends all logs directly to both destinations.
D) Write all logs to Heroku Redis as a buffer and use an add-on to send them to both destinations.
3. Which two logs and logging recommendations are prescribed by the Twelve-Factor app methodology?
Choose 2 answers.
A) Apps should only keep a limited, rolling buffer of logs available
B) Apps should not concernthemselves with routing or storing logs
C) Logs from all processes and backing services should be aggregated together.
D) Logs should be written to a shared file system for scalability.
4. To satisfy the requirements of an upcoming compliance audit, a client must provide a record of all interactive commands run against a production application in the last six months. Which Heroku feature should an Architect recommend to help with this use case?
A) Dataclips
B) SSH tunneling using Heroku Exec
C) Private Space Logging
D) Heroku Shield keystroke logging
5. Which of thefollowing is a good use case for the Heroku Platform?
A) Customer engagement applications
B) All of these
C) Empowering mobile apps with an API service
D) Data manipulation
E) Proof-of-concept or lab approaches
Solutions:
| Question # 1 Answer: A | Question # 2 Answer: A | Question # 3 Answer: B,C | Question # 4 Answer: D | Question # 5 Answer: A |
By Zoe
