Drupal Acquia Cloud , DAM and Cloud Hub Interview questions

 

What is Acquia Cloud and how is deployment handled there?

Acquia Cloud is a managed Drupal hosting platform built on AWS that provides autoscaling, security, CI/CD pipelines, and monitoring tools like Insight and New Relic. Code deployment is Git-based — we push code to the repository, and Acquia pipelines promote the branch to Dev, Stage, or Prod environments. Production is read-only, ensuring controlled deployments.

Explain the complete flow of content synchronization using Acquia Content Hub.

In Content Hub, a publisher site sends selected entities to Acquia Cloud in CDF format. Subscriber sites, configured with Acquia credentials, periodically pull this data via cron-triggered queue workers. The subscriber recreates the entities in its local database using UUID mapping.

Why does Content Hub use UUID instead of Node ID?

Node IDs differ across sites, but UUID is globally unique for each entity. Content Hub uses UUID to correctly identify whether to create or update an entity on subscriber sites, ensuring consistent synchronization.

How does a subscriber site know when to pull content from the hub?

Subscriber sites do not receive real-time notifications. Instead, Drupal cron triggers Content Hub queue workers that poll the hub, fetch pending CDF items, and process them locally.

What problem does Acquia DAM solve that Drupal Media Library cannot?

Drupal Media Library stores files locally within a site, whereas Acquia DAM is a centralized asset governance system. DAM provides versioning, metadata, approval workflows, and controlled access. Drupal sites reference assets from DAM via API instead of storing them.

Difference between Multisite and Content Hub?

Multisite shares the same codebase with separate databases for structural reuse. Content Hub shares content across completely independent Drupal sites for content governance.

Multisite shares code, Content Hub shares content.

In a multisite setup, how do you enable a module only for one site?

Even though the codebase is shared, module enablement is stored in each site's configuration database. So we enable the module only on the required site.

How do you manage configuration separately for each site in multisite with Git?

In multisite with config management, I define separate config sync directories in each site’s settings.php to prevent configuration overlap, ensuring site-specific modules and settings remain isolated.

How do cache contexts help in multilingual Drupal sites?

Cache context languages ensures Drupal stores separate cache versions per language. This prevents translated content from being served incorrectly across languages.

Production site is slow but Dev is fast in Acquia — how do you troubleshoot?

I would use Acquia Insight, New Relic, logs, and slow query analysis to identify bottlenecks. Typically, issues relate to caching layers, database load, or external integrations that behave differently in production.