Cloud Pro

← All exam tracks

Acquia Cloud Platform

Cloud Pro

Practice original scenario-based Cloud Pro questions. Take a timed mock, focus on a topic, and learn from detailed explanations. These are independent practice materials, not official exam questions or a guarantee of certification readiness.

40 questions · 60 minutes · 65% practice target

Create an account to practice Already a member? Sign in

Topics you will practice

  • Hosting Fundamentals
  • Platform Features
  • Cloud Workflow
  • Best Practices

Try a sample

Think through each question, then reveal the explanation. Full attempts save your answers and scores to your account.

Anonymous HTML is a Varnish HIT, but its embedded recommendation fragment is user-specific and has appeared for the wrong visitor. Origin responses are correct. What should the team investigate first?

  1. Whether the shared-cache key and cacheability headers vary or bypass correctly for the personalized response
  2. Whether MySQL replication copied the recommendation quickly enough
  3. Whether the Git branch contains the latest Twig template
  4. Whether the shared files mount has identical permissions on every web node
Show answer and explanation

Correct answer: Whether the shared-cache key and cacheability headers vary or bypass correctly for the personalized response

Correct origin output combined with incorrect shared reuse points to cache variation or bypass rules. Personalized content must not be shared under a cache key that omits its varying inputs.

A Drupal application stores user-uploaded images that must be available to all web nodes. Which shared infrastructure component serves this purpose?

  1. Git repository
  2. Network file system
  3. PHP OPcache
  4. Local browser cache
Show answer and explanation

Correct answer: Network file system

The shared network file system makes uploaded files available across the application’s web servers. Git is for code, not runtime uploads.

A team wants changes reviewed and tested before production. Which workflow is most appropriate?

  1. Edit production code over SSH
  2. Develop locally, commit to Git, deploy to a non-production environment, test, then promote
  3. Upload code directly to every web node
  4. Make all changes through the production UI
Show answer and explanation

Correct answer: Develop locally, commit to Git, deploy to a non-production environment, test, then promote

A version-controlled, environment-based workflow makes changes repeatable, reviewable, and testable before production.