I85PREP
⌘ K
Acquia Cloud Pro study materials
Acquia Cloud Pro study resources

Acquia Cloud Pro practice questions

One question at a time. Build your Acquia Cloud Pro understanding.

First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1Acquia Cloud Platform architecture and environments

In Acquia Cloud, which environment is intended for final pre-production validation and typically mirrors the production environment's configuration?

  1. The development environment
  2. The local development environment
  3. The staging environment Correct answer.
  4. The production environment

Explanation

Acquia Cloud provides a standard workflow of dev, stage, and prod environments per application. The staging environment is a clone of production used to validate changes before deployment to prod.

Question 2Acquia Cloud Platform architecture and environments

What is the primary purpose of the Acquia Cloud development environment in the standard workflow?

  1. To store database backups for disaster recovery
  2. To integrate and test code changes before promotion Correct answer.
  3. To serve live traffic to end users
  4. To host the CDN origin for production

Explanation

The dev environment is where developers push and integrate code and run initial testing. Changes are then promoted to stage and finally production.

Question 3Acquia Cloud Platform architecture and environments

In Acquia Cloud, code is deployed to an environment by pushing to a branch in the application's Git repository. Which statement describes how a Git branch maps to an environment?

  1. Each environment requires its own separate repository with no shared history
  2. Each environment is bound to a specific branch, and pushing to that branch triggers a deployment to it Correct answer.
  3. All environments share a single branch and deployments are selected by tag
  4. Environments are mapped to Git remotes rather than branches

Explanation

Acquia Cloud associates each environment with a branch of the application's repository. Pushing commits to an environment's branch deploys that code to the corresponding environment.

Question 4Acquia Cloud Platform architecture and environments

A developer wants to deploy code to the staging environment. What is the standard Acquia Cloud mechanism to do so?

  1. Merge directly into the production branch and wait for sync
  2. Push commits to the branch associated with the staging environment Correct answer.
  3. Run a drush command that copies files from prod
  4. Upload a zip file through the Cloud UI only

Explanation

Deploying to an environment is done by pushing code to that environment's associated Git branch. The platform then builds and deploys the code.

Question 5Acquia Cloud Platform architecture and environments

Which Acquia Cloud component provides a shared, network-attached filesystem where Drupal's public files directory resides across web servers?

  1. The Varnish cache layer
  2. The distributed file system (shared filesystem) Correct answer.
  3. The load balancer
  4. The database cluster

Explanation

Acquia Cloud uses a distributed file system so that files uploaded to one web server are available to all web servers in the environment. The public files directory lives on this shared storage.

Question 6Acquia Cloud Platform architecture and environments

Why does Acquia Cloud route requests through Varnish before they reach the web servers?

  1. To terminate TLS certificates for the domain
  2. To balance traffic between the database nodes
  3. To store session data for authenticated users
  4. To cache anonymous HTTP responses and reduce load on the web tier Correct answer.

Explanation

Varnish sits in front of the web servers as an HTTP reverse proxy cache. It serves cached anonymous page responses, reducing requests that reach the application and improving performance.

Question 7Acquia Cloud Platform architecture and environments

In the Acquia Cloud request path, what is the role of the load balancer tier?

  1. It compiles Twig templates for the application
  2. It stores the Drupal database and serves SQL queries
  3. It distributes incoming traffic across web servers and handles TLS termination Correct answer.
  4. It runs cron jobs for all environments

Explanation

The load balancer receives client requests, terminates TLS, and spreads traffic across the environment's web servers. This provides availability and horizontal scaling.

Question 8Acquia Cloud Platform architecture and environments

What does the Acquia Cloud database tier provide for a production environment?

  1. An in-memory cache replacing the need for persistent storage
  2. A NoSQL document store used in place of MySQL
  3. A single MySQL instance shared by all applications on the platform
  4. A managed MySQL cluster with a primary and at least one replica Correct answer.

Explanation

Acquia Cloud provides a managed MySQL cluster for production environments, with a primary node and replica(s) for redundancy and read scaling. The platform handles replication and failover.

Question 9Acquia Cloud Platform architecture and environments

A team needs to copy the production database down to the staging environment to test with realistic data. Which statement best describes how this is accomplished in Acquia Cloud?

  1. Staging reads directly from the production database over a private link
  2. Databases are automatically replicated from prod to stage in real time
  3. An operator initiates a database copy from the source environment to the destination using the platform tools Correct answer.
  4. Database copies are only possible between dev and stage, never from prod

Explanation

Acquia Cloud lets you copy a database from one environment to another on demand, typically prod to stage or dev. The copy is initiated explicitly rather than being a continuous replication between environments.

Question 10Acquia Cloud Platform architecture and environments

Which statement correctly describes how the Acquia Cloud workflow separates environments for a single application?

  1. Each environment has its own code branch, database, and files, isolated from the others Correct answer.
  2. The dev environment has no database and reads from stage
  3. All environments share one database to keep data consistent
  4. Environments share a single filesystem so uploads are instantly available everywhere

Explanation

Each environment is an isolated stack with its own code branch, database, and file storage. This isolation lets teams test changes without affecting other environments.

Question 11Acquia Cloud Platform architecture and environments

What is the purpose of the Acquia Cloud 'ra' (remote administration) toolset available on environments?

  1. To run administrative commands such as database copies and backups against an environment Correct answer.
  2. To provision new servers in the load balancer tier
  3. To configure Varnish caching rules directly
  4. To replace Git for deploying code

Explanation

Acquia Cloud provides command-line tooling (commonly invoked through the 'ra' wrapper in older toolchains) to perform administrative operations like backups, database copies, and cache clears on an environment.

Question 12Acquia Cloud Platform architecture and environments

An application needs a custom domain name pointed at its production environment. Which DNS record type is typically used to point the domain at the Acquia load balancer?

  1. An MX record
  2. A CNAME record Correct answer.
  3. A TXT record
  4. An SRV record

Explanation

Custom domains are pointed at Acquia using DNS records that resolve to the environment's load balancer, commonly a CNAME (or A records for apex domains via supported methods). MX, TXT, and SRV serve unrelated purposes.

Question 13Acquia Cloud Platform architecture and environments

Which statement about SSL/TLS certificates on Acquia Cloud is accurate?

  1. Certificates are managed at the load balancer layer for the environment's domains Correct answer.
  2. Each web server generates its own self-signed certificate for production
  3. TLS is disabled by default and cannot be enabled
  4. Certificates are stored in the Drupal codebase and served by PHP

Explanation

TLS termination occurs at the load balancer tier, where the environment's certificates are installed for its domains. Traffic is then passed to the web tier within the platform's network.

Question 14Acquia Cloud Platform architecture and environments

A developer wants to verify a code change without affecting production users. What is the most appropriate environment to deploy the change to first?

  1. The development environment, then promote to stage Correct answer.
  2. The database replica
  3. The load balancer tier
  4. Production, then roll back if problems occur

Explanation

Changes should be deployed to the development environment first, then promoted through staging before production. This follows the standard dev-to-stage-to-prod promotion workflow.

Question 15Acquia Cloud Platform architecture and environments

What does the Acquia Cloud 'clear caches' operation on an environment typically clear?

  1. The Git repository's commit history
  2. Only the Memcached session store
  3. The Varnish cache and the Drupal caches on the web tier Correct answer.
  4. Only the Drupal database cache tables

Explanation

Clearing caches on an environment purges the Varnish HTTP cache and triggers Drupal cache rebuilds on the web tier. This ensures updated content and code are served.

Question 16Acquia Cloud Platform architecture and environments

Which Acquia Cloud feature allows an application to use additional services such as Solr search?

  1. Acquia Cloud's managed service integrations attached to the environment Correct answer.
  2. The Varnish cache configuration
  3. The load balancer's health checks
  4. The Git branch protection rules

Explanation

Acquia Cloud offers managed service integrations, including Apache Solr search, that are attached to environments. Applications connect to these services through environment configuration.

Question 17Acquia Cloud Platform architecture and environments

How does Acquia Cloud handle multiple web servers within a production environment to support scaling?

  1. It runs a single web server that is vertically resized on demand
  2. It serves all requests directly from the database tier
  3. It runs one web server per environment with no scaling
  4. It runs multiple web servers behind the load balancer, sharing the distributed filesystem Correct answer.

Explanation

Production environments can run multiple web servers positioned behind the load balancer. They share the distributed filesystem so any server can handle any request.

Question 18Acquia Cloud Platform architecture and environments

What is the recommended practice for managing configuration (such as settings.php overrides) across Acquia Cloud environments?

  1. Commit environment-specific settings to each environment's branch and keep secrets out of the repository Correct answer.
  2. Edit settings.php directly on the server and never commit it
  3. Store all secrets in the database and read them at runtime
  4. Hardcode production credentials in the shared codebase

Explanation

Environment-specific configuration should be managed per branch, with sensitive values kept out of version control and supplied through environment variables or secure mechanisms. This keeps environments consistent while protecting secrets.

Question 19Acquia Cloud Platform architecture and environments

Which statement best describes how Acquia Cloud isolates environments from one another at the infrastructure level?

  1. Environments share a filesystem but have separate databases
  2. All environments share the same web servers and database
  3. Each environment runs its own set of servers, database, and filesystem Correct answer.
  4. Only production has dedicated servers; stage and dev share production's resources

Explanation

Each environment is provisioned with its own servers, database, and filesystem, providing isolation. This prevents changes or load in one environment from affecting another.

Question 20Acquia Cloud Platform architecture and environments

A team wants to test a Drupal core upgrade with production-like data before going live. Which sequence best follows Acquia Cloud's environment model?

  1. Upgrade on production, then copy back to stage if it fails
  2. Upgrade only on the load balancer tier
  3. Upgrade directly on the database replica
  4. Upgrade on dev, copy the prod database to stage, deploy to stage and test, then deploy to prod Correct answer.

Explanation

The safe workflow is to develop and upgrade on dev, refresh stage with a copy of production data, validate on stage, then promote to production. This uses the environment tiers as intended.

Question 21Acquia Cloud Platform architecture and environments

What is the role of the Acquia Cloud 'Cloud UI' or API regarding environments?

  1. It provisions new hardware for the load balancer
  2. It lets operators view environments and perform actions such as backups, copies, and cache clears Correct answer.
  3. It edits Drupal PHP files directly on the server
  4. It replaces Git as the mechanism for deploying code

Explanation

The Cloud UI and API provide operational control over environments, including backups, database copies, cache clears, and monitoring. Code deployment itself remains Git-driven.

Question 22Acquia Cloud Platform architecture and environments

Which statement about the Acquia Cloud filesystem for a production environment is correct?

  1. The filesystem is shared across web servers so uploads are consistent Correct answer.
  2. Each web server has a private filesystem and uploads are not shared
  3. The filesystem is read-only and uploads are disabled
  4. The filesystem is stored in the database as blobs

Explanation

Acquia Cloud uses a distributed filesystem shared across the environment's web servers. Files uploaded through any server are available to all servers, keeping content consistent.

Question 23Acquia Cloud Platform architecture and environments

A developer pushes a hotfix to the production branch. What happens next in the Acquia Cloud deployment process?

  1. The database is automatically rolled back
  2. The load balancer is reconfigured with new certificates
  3. The platform builds and deploys the code to the production environment Correct answer.
  4. The code is automatically copied to stage for review

Explanation

Pushing to the branch associated with an environment triggers a build and deployment to that environment. A push to the production branch deploys to production.

Question 24Acquia Cloud Platform architecture and environments

What is the primary benefit of using Varnish in front of Drupal on Acquia Cloud for anonymous traffic?

  1. It serves cached pages without invoking PHP, reducing backend load Correct answer.
  2. It compiles PHP opcode for faster execution
  3. It rebalances the database cluster
  4. It encrypts database connections

Explanation

Varnish caches full HTTP responses for anonymous users, serving them directly without hitting PHP or the database. This dramatically reduces backend load and improves response times.

Question 25Acquia Cloud Platform architecture and environments

Which statement accurately describes the relationship between an Acquia Cloud application and its environments?

  1. An application's environments must all use the same branch
  2. An application can have multiple environments such as dev, stage, and prod Correct answer.
  3. An application has exactly one environment
  4. Environments exist independently of any application

Explanation

An Acquia Cloud application is a container for multiple environments, typically dev, stage, and prod. Each environment is a separate deployment of the application with its own branch, database, and files.

Question 26Acquia Cloud Platform architecture and environments

What does the Acquia Cloud 'ra' (remote administration) toolset available on environments primarily provide?

  1. A network appliance that terminates TLS connections before the load balancer
  2. A graphical dashboard for reviewing subscription billing and invoice history
  3. A browser extension that highlights deprecated Drupal APIs in rendered pages
  4. A command-line interface for running operations such as database access and file transfers against a specific environment Correct answer.

Explanation

The ra toolset exposes environment-scoped commands over SSH, letting developers run database imports/exports, file syncs, and other operational tasks against a chosen environment. It is an administrative command-line layer, not a billing or browser tool.

Question 27Acquia Cloud Platform architecture and environments

Which DNS record type is typically used to point a custom domain at an Acquia Cloud production environment?

  1. TXT
  2. CNAME Correct answer.
  3. MX
  4. SRV

Explanation

A CNAME record maps the custom hostname to the platform-provided hostname for the environment, letting Acquia manage the underlying address. MX handles mail routing, TXT holds arbitrary text such as verification strings, and SRV advertises service locations.

Question 28Acquia Cloud Platform architecture and environments

How does Acquia Cloud isolate environments from one another at the infrastructure level?

  1. All environments share a single database and filesystem, with isolation enforced only by Drupal permissions
  2. Isolation is achieved by assigning each environment a different PHP version
  3. Environments are isolated only by separate Git branches, with shared runtime resources
  4. Each environment runs on its own set of servers and has its own database and filesystem Correct answer.

Explanation

Each environment is provisioned as a distinct stack with its own web servers, database, and file storage, so activity in one environment does not touch another. Code branches and configuration are separate concerns layered on top of that infrastructure separation.

Question 29Acquia Cloud Platform architecture and environments

A team needs to copy the production database down to the staging environment to test with realistic data. Which statement about this operation on Acquia Cloud is correct?

  1. The database can be copied between environments of the same application using the platform's environment-copy workflow Correct answer.
  2. Cross-environment database copies are impossible because environments share one database
  3. Copying requires exporting to a local machine and re-importing through the Drupal UI
  4. Databases can only be copied upward from dev to prod, never downward

Explanation

The platform supports copying a database from one environment to another within the same application, which is the standard way to refresh staging with production-like data. The operation does not require a manual round trip through a local machine.

Question 30Acquia Cloud Platform architecture and environments

Which Acquia Cloud capability allows an application to use an additional service such as Solr search?

  1. Enabling a Drupal module that bundles its own Solr server process
  2. Adding a service to the environment through the platform, which provisions and connects the service Correct answer.
  3. Requesting a separate application whose only purpose is to host Solr
  4. Installing a Solr binary directly on each web server via SSH

Explanation

Additional services are attached to an environment through the platform, which provisions the service and supplies connection details to the application. Manually installing server software on web servers is not how platform services are delivered.

Question 31Acquia Cloud Platform architecture and environments

What is the recommended practice for managing configuration such as settings.php overrides across Acquia Cloud environments?

  1. Use environment-specific include files driven by environment variables so each environment loads its own settings Correct answer.
  2. Commit a single settings.php containing production credentials for all environments
  3. Store all configuration in the database and never version it in Git
  4. Edit settings.php directly on each server through SSH after every deployment

Explanation

Environment-specific includes keyed off environment variables let one codebase adapt to dev, staging, and prod without hardcoding secrets or editing files on servers. This keeps configuration versioned while remaining environment-aware.

Question 32Acquia Cloud Platform architecture and environments

A developer pushes a commit to the production branch. What happens next in the Acquia Cloud deployment process?

  1. The commit is automatically deployed to every environment in the application at once
  2. The commit is deployed to the production environment's codebase, and the change becomes live once the code is built and caches are refreshed Correct answer.
  3. The commit is held in a queue until an Acquia support engineer approves it manually
  4. The commit is rejected unless it also exists on the dev branch first

Explanation

Pushing to an environment's branch triggers deployment of that branch's code to the corresponding environment. Once the code is in place and caches are cleared, the change is served to users; no manual vendor approval step is involved.

Question 33Acquia Cloud Platform architecture and environments

What is the role of the Acquia Cloud Cloud UI and API with respect to environments?

  1. They replace Git entirely by storing and versioning all application code
  2. They act as the DNS provider for all custom domains attached to applications
  3. They serve as the runtime web server that executes PHP for production traffic
  4. They provide interfaces for managing environments, such as creating them, copying data between them, and triggering operations Correct answer.

Explanation

The Cloud UI and API are management interfaces: they let teams perform environment operations like creating environments, copying databases and files, and clearing caches. They orchestrate the platform but do not execute application code or replace version control.

Question 34Acquia Cloud Platform architecture and environments

A team wants to test a Drupal core upgrade with production-like data before going live. Which sequence best follows Acquia Cloud environment practices?

  1. Test the upgrade locally with an empty database, then push to production without further validation
  2. Copy the production database and files to staging, deploy the upgrade branch to staging, test there, then deploy the tested code to production Correct answer.
  3. Deploy the upgrade directly to production, then copy production back to staging to verify it
  4. Run the upgrade on the dev environment only and promote dev straight to production without staging

Explanation

Refreshing staging with production data and testing the upgrade there reproduces realistic conditions without risk to live users. Only after validation is the tested code deployed to production.

Question 35Acquia Cloud Platform architecture and environments

An application's production environment has multiple web servers, but a module writes cache files to a local directory on each server. What is the most likely consequence and best remedy?

  1. Cached data diverges between servers, so the code should write to shared storage or a shared cache backend instead Correct answer.
  2. Nothing changes, because local writes are automatically replicated to all web servers
  3. The load balancer detects the local writes and pins each user to the server that wrote them
  4. Only the first web server receives traffic, so the other servers' local caches are irrelevant

Explanation

With several web servers, local-only writes create inconsistent state because each server has its own filesystem view. Directing that data to shared storage or a shared cache service makes the state consistent across the fleet.

Question 36Acquia Cloud Platform architecture and environments

In Acquia Cloud, what is the purpose of a codebase's 'tags' in relation to deployments?

  1. They are DNS aliases assigned to load balancers for each environment.
  2. They are database backups captured automatically before each deployment.
  3. They are immutable snapshots of a branch used to build a deployable artifact for an environment. Correct answer.
  4. They are the primary working branches where developers commit daily changes.

Explanation

Acquia Cloud builds deployment artifacts from Git tags, which are immutable references to a specific commit. Tags let you deploy a known, reproducible state to an environment rather than whatever happens to be at the branch tip. Branches remain the mutable places where development work happens.

Question 37Acquia Cloud Platform architecture and environments

Which statement describes how Acquia Cloud associates a custom domain with a specific environment?

  1. Domain mapping requires editing the Drupal settings.php file to hardcode the hostname per environment.
  2. A custom domain must be added as a Git remote before it can serve traffic for an environment.
  3. Custom domains can only be attached to the production environment because non-production environments lack load balancers.
  4. Each environment gets its own automatic wildcard subdomain, and custom domains are mapped to an environment through the platform's domain settings. Correct answer.

Explanation

Acquia Cloud gives every environment a platform-provided hostname and lets you add custom domains to the environment you want to serve them. The mapping is configured in the platform, not in application code. Non-production environments can also have domains attached.

Question 38Acquia Cloud Platform architecture and environments

A team maintains separate dev, staging, and production environments on Acquia Cloud. They want a code change validated on staging before it reaches production. Which workflow aligns with the platform's environment model?

  1. Merge staging into production locally and push the result only to the staging remote.
  2. Deploy the tested tag to staging, verify it, then deploy that same tag to production. Correct answer.
  3. Copy the production database into dev and treat dev as the release candidate environment.
  4. Commit directly to the production branch and rely on automatic rollback if tests fail.

Explanation

Because environments are built from deployable artifacts, promoting the same tested tag from staging to production preserves exactly what was validated. This avoids untested drift between environments. Direct commits to production bypass the validation step.

Question 39Acquia Cloud Platform architecture and environments

An application on Acquia Cloud needs a persistent, shared writable location for user-uploaded files across multiple web servers. Which platform component fulfills this requirement?

  1. A shared filesystem volume mounted across the environment's web servers. Correct answer.
  2. The Varnish caching layer in front of the web tier.
  3. The Drupal database's blob columns.
  4. The local ephemeral disk of each web server.

Explanation

Acquia Cloud provides a shared filesystem so that files written by one web server are visible to all web servers in the environment. Local disk is not shared and does not persist reliably across servers. The database and Varnish serve different purposes.

Question 40Acquia Cloud Platform architecture and environments

An architect is comparing how Acquia Cloud delivers a Drupal page for an anonymous visitor versus a logged-in user. Which analysis best reflects the platform's caching architecture?

  1. Varnish is disabled for production environments and only operates in non-production environments for testing.
  2. Authenticated requests are served from Varnish and anonymous requests always reach Drupal because anonymous users have no session cookie.
  3. Anonymous requests can be served from the Varnish layer, while authenticated requests typically bypass Varnish and are handled by Drupal with its own caching layers. Correct answer.
  4. Both anonymous and authenticated requests are served identically from Varnish because Varnish caches all responses regardless of session.

Explanation

Varnish caches responses for anonymous traffic, dramatically reducing load on the web tier. Requests carrying session state, such as those from logged-in users, are passed through to Drupal, which applies its own caching. This division is central to Acquia Cloud's performance model.

Question 41Deployment workflow and code management

In an Acquia Cloud environment, what is the primary function of a code branch that has been deployed to the Dev environment?

  1. It automatically rewrites the Drupal settings.php file on every commit.
  2. It stores only database backups taken from the Production environment.
  3. It builds and serves the application code for that environment, and can be deployed forward to higher environments. Correct answer.
  4. It is a read-only archive that cannot receive new commits.

Explanation

Branches in Acquia Cloud are the unit of deployment: a branch is built into an artifact and served by the environment it is deployed to. The same branch can then be promoted forward to Test and Prod via the deployment pipeline.

Question 42Deployment workflow and code management

Which git remote/URL should a developer push to in order to update the code on an Acquia Cloud environment?

  1. A local bare repository created on the developer workstation.
  2. The Acquia-hosted git repository remote provided for the application. Correct answer.
  3. The production web server's document root over SFTP.
  4. A third-party mirror that is polled hourly.

Explanation

Acquia Cloud hosts a git repository per application; pushing to that remote is what makes commits available for deployment to environments. Direct file edits or unrelated remotes do not participate in the build and deploy pipeline.

Question 43Deployment workflow and code management

What does deploying a branch to the Test environment in Acquia Cloud do with respect to the existing database?

  1. It merges the Dev and Prod databases automatically.
  2. It leaves the Test database intact unless a database copy is separately performed. Correct answer.
  3. It always drops and recreates the Test database from Prod.
  4. It exports the database to the code branch.

Explanation

A code deployment only deploys code; databases are handled by explicit database copy or backup/restore operations. Deploying code does not implicitly refresh or destroy the target environment's database.

Question 44Deployment workflow and code management

A team wants changes made on the Dev environment to reach Production. Which workflow matches Acquia Cloud's deployment model?

  1. Edit code in the Prod environment's UI and rely on it syncing back to git.
  2. Copy files from Dev's docroot to Prod's docroot using a file sync tool.
  3. Commit to the branch, deploy that branch to Dev, then deploy the same branch to Test, then to Prod. Correct answer.
  4. Push directly to a Prod-only branch that skips Dev and Test.

Explanation

Acquia Cloud's pipeline promotes the same code artifact forward from Dev to Test to Prod. Each stage deploys the branch artifact rather than copying files between servers.

Question 45Deployment workflow and code management

What is an artifact in the context of Acquia Cloud deployments?

  1. A built, immutable snapshot of the code branch that is deployed to an environment. Correct answer.
  2. A configuration file listing environment variables.
  3. A git tag that marks a release.
  4. A database dump generated during a backup.

Explanation

When a branch is deployed, Acquia builds an artifact from the branch (including dependency build steps) and deploys that artifact. The artifact is what the environment actually runs.

Question 46Deployment workflow and code management

Which statement about the relationship between a git tag and a deployment in Acquia Cloud is accurate?

  1. Tags automatically trigger a database copy to Prod when pushed.
  2. Tags are ignored by Acquia Cloud and cannot be deployed.
  3. Tags can be deployed as code references and provide a stable pointer to a specific commit. Correct answer.
  4. Tags replace the need for branches in the deployment pipeline.

Explanation

Acquia Cloud supports deploying a tag as well as a branch; a tag gives a fixed reference to a commit for reproducible deployments. Tags do not, by themselves, perform database operations or replace branches.

Question 47Deployment workflow and code management

A developer needs to deploy a hotfix to Production while keeping the main development line unaffected. What is the most appropriate approach?

  1. Revert the entire repository to an earlier commit on all environments.
  2. Commit the fix to the main branch and deploy the main branch to Prod immediately.
  3. Create a hotfix branch from the production code, commit the fix, and deploy that branch to Prod. Correct answer.
  4. Edit the file directly on the Prod server and commit later.

Explanation

A hotfix branch isolates the change so it can be deployed to Prod without pulling in unrelated in-progress work. The fix can later be merged back into the main development line.

Question 48Deployment workflow and code management

What is the purpose of the `settings.php` include mechanism that Acquia Cloud provides for environment-specific configuration?

  1. It forces all environments to share a single database connection string.
  2. It compiles SCSS and JavaScript during deployment.
  3. It lets each environment load its own database credentials and configuration without editing tracked code. Correct answer.
  4. It replaces git as the source of configuration truth.

Explanation

Acquia Cloud injects environment-specific settings (such as database credentials) so the same codebase can run correctly in Dev, Test, and Prod. This keeps secrets and per-environment values out of version control.

Question 49Deployment workflow and code management

Which action is required before a newly created branch can be deployed to an Acquia Cloud environment?

  1. The branch must be approved by Acquia support.
  2. The branch must be merged into the master branch first.
  3. The branch must be pushed to the Acquia-hosted git repository. Correct answer.
  4. The branch must be converted to a tag.

Explanation

Acquia Cloud builds deployments from branches present in its hosted repository, so the branch must be pushed there before it can be selected for deployment. Merging, tagging, or support approval are not prerequisites.

Question 50Deployment workflow and code management

A team observes that a deployment to Prod succeeded but a new module's code is missing. Which is the most likely cause?

  1. The commit containing the module was not included in the branch that was deployed. Correct answer.
  2. The Prod database was not copied from Test first.
  3. The Prod environment lacks a settings.php file.
  4. The module was not enabled in the Dev environment's UI.

Explanation

Deployment ships the artifact built from the selected branch; code not committed to that branch will not be present. Database copies and UI enablement do not add missing code files.