Free Plat-Arch-206 sample questions

Correct answer: Upgrade to Performance-L dynos and configure the Heroku Autoscaler to scale based on response time.

For high-traffic events, upgrading to Performance dynos is recommended because they run on dedicated hardware with consistent performance. The Heroku Autoscaler is specifically available for Performance-tier dynos and can automatically scale the dyno count up during the spike and down afterwards based on response latency, balancing reliability and cost.

Correct answer: Use a `.slugignore` file to exclude static assets and large binaries that are not required at runtime.

The `.slugignore` file functions similarly to `.gitignore` but specifically for the slug compiler. By excluding large files (like design assets, raw data, or test binaries) that aren't needed for the application to run, you directly reduce the slug size. This is the architectural best practice for managing slug size limits.

Correct answer: True

Heroku automatically cycles dynos approximately every 24 hours (plus or minus a random window) to maintain the health of the underlying fleet. This happens across all plan levels in the Common Runtime. Architects must design applications to be stateless and handle these graceful restarts without user disruption.

Correct answers: Heroku Private Spaces; DNS Service Discovery

Heroku Private Spaces provide the isolated network environment required for private communication between apps (via DNS Service Discovery) and offer stable outbound IP addresses by default, which is a core requirement.

DNS Service Discovery is the mechanism within a Private Space that allows apps to locate and communicate with each other using internal naming conventions (e.g., `app-name.space-name.local`) without exposing endpoints to the public internet.

Correct answer: Provision a Follower Database for the reporting app and configure the dashboard to connect to the Follower's URL.

Heroku Postgres Follower databases are read-only replicas that asynchronously replicate data from the primary (leader) database. By pointing the reporting dashboard to a Follower, the heavy read queries are executed against the replica, completely isolating the primary database's resources for the transaction app's write operations. This prevents table locking on the primary.

Correct answer: Scale the worker process vertically to a larger dyno type (e.g., from Standard-1x to Standard-2x) to provide more RAM.

R14 errors indicate the process is consuming more memory than the dyno provides, causing paging to disk and performance degradation. Since the issue is related to processing large single items (images), adding more dynos (horizontal scaling) won't help. The correct approach is vertical scaling to a dyno type with more memory capacity.