Career upgrade: Learn practical AI skills for better jobs and higher pay.
Level up
All Practice Exams

100+ Free Acquia Site Factory Pro Practice Questions

Pass your Acquia Certified Site Factory Pro exam on the first try — instant access, no signup required.

✓ No registration✓ No credit card✓ No hidden fees✓ Start practicing immediately
~65-75% Pass Rate
100+ Questions
100% Free
1 / 100
Question 1
Score: 0/0

Which two factory-hook events are most directly tied to the deploy lifecycle, rather than the request lifecycle?

A
B
C
D
to track
2026 Statistics

Key Facts: Acquia Site Factory Pro Exam

65%

Passing Score

Acquia

60 Qs

Question Count

Acquia

75 min

Exam Duration

Acquia

$155

Exam Fee

Acquia

30-60 hrs

Study Time

Recommended

2 years

Cert Valid

Acquia

The Acquia Certified Site Factory Pro exam is scenario-based with 60 multiple-choice questions in 75 minutes and a 65% passing score. It tests Acquia Cloud Site Factory (ACSF) skills: Site Collections, Sites and site copies, factory-hooks (pre/post-sites-php, pre-settings-php, db-update), the ACSF Connector module, SAML SSO, code deploys via Git tags, backup and restore, User Sync, the ACSF REST API, sf-toolbelt drush aliases, and the Site Owner/Platform Admin/Domain Admin role model.

Sample Acquia Site Factory Pro Practice Questions

Try these sample questions to test your Acquia Site Factory Pro exam readiness. Each question includes a detailed explanation. Start the interactive quiz above for the full 100+ question experience with AI tutoring.

1What is Acquia Cloud Site Factory (ACSF)?
A.A multi-site Drupal management platform built on top of Acquia Cloud
B.A single-application Drupal hosting subscription
C.A standalone Drupal distribution
D.A content delivery network managed by Acquia
Explanation: Acquia Cloud Site Factory (ACSF) is a multi-site Drupal management platform that runs on top of Acquia Cloud. It lets a single team operate hundreds or thousands of Drupal sites from one shared codebase, with centralized site creation, role management, code deployments, backups, and a single control plane. The Site Factory Pro exam treats this as foundational: ACSF is not a replacement for Acquia Cloud, it is an additional layer that adds multi-site orchestration on top of the Cloud Platform.
2In ACSF terminology, what is a Site Collection?
A.A backup archive containing all sites in the factory
B.A logical grouping of related sites that share environments and a codebase
C.A single Drupal site instance
D.A custom domain group used for SSL provisioning
Explanation: A Site Collection in ACSF is a logical grouping of related Drupal sites that share the same codebase and the same Stage/Prod environments. Site Collections are how you split a factory between, for example, a marketing-sites group and a product-sites group, where each group needs its own deployment cadence. Sites within a collection share code; sites in different collections can be on different code branches or releases.
3Which role in ACSF can create new sites across the entire factory, manage the codebase, and configure factory-level settings?
A.Site Owner
B.Domain Admin
C.Platform Admin
D.Anonymous
Explanation: Platform Admin is the highest-scope role in ACSF. A Platform Admin can create new sites anywhere in the factory, configure factory-level settings, manage Site Collections, manage all users and roles, and operate the codebase deployment workflow. Site Owners are scoped to the specific sites they own, and Domain Admins are scoped to custom domain management for the sites they administer.
4What is the primary purpose of the ACSF Connector Drupal module?
A.To enable Varnish caching on each site
B.To proxy database connections through Acquia Cloud
C.To replace Drupal core with an ACSF-specific build
D.To broker communication between an individual Drupal site and the Site Factory control plane
Explanation: The ACSF Connector is a Drupal module that must be installed and enabled on every site in the factory. It brokers communication between the individual Drupal site and the Site Factory control plane. The Connector handles SSO sign-in, User Sync, ACSF REST API integration, site duplication, and the factory's site lifecycle hooks. Without the Connector enabled, a site cannot be fully managed by Site Factory.
5How are code deployments delivered to sites in an ACSF Site Collection?
A.A Git tag is pushed to the shared ACSF codebase repo and deployed to all sites in the collection at once
B.Each site has its own Git branch deployed independently
C.Code is uploaded as a tarball through the ACSF UI
D.Each site pulls code via composer install on a schedule
Explanation: All sites within an ACSF Site Collection share a single codebase, and code is deployed by pushing a Git tag to the shared ACSF codebase repository and selecting that tag in the Site Factory UI (or via the ACSF REST API). The deployment then rolls the code out to every site in the collection. This is fundamentally different from Acquia Cloud Pro, where each application has its own repo and you deploy a branch or tag per application.
6Which factory-hook runs to modify the dynamically generated sites.php during the site bootstrap process?
A.post-db-copy
B.pre-sites-php
C.post-files-copy
D.pre-deploy
Explanation: The pre-sites-php factory-hook fires before ACSF writes out the sites.php file that maps incoming domains to specific site directories. Using pre-sites-php you can inject additional domain-to-site mappings, transform the data ACSF will write, or add custom logic that must run before sites.php is finalized. The post-sites-php hook then fires after sites.php is written, useful for caching warm-up or notifications.
7Where in the codebase repository do factory-hooks live?
A./docroot/hooks
B./sites/all/hooks
C./factory-hooks at the repo root
D./var/www/hooks
Explanation: Factory-hooks live in a top-level directory named factory-hooks at the root of the ACSF codebase repository. Inside factory-hooks, each lifecycle event (pre-sites-php, post-sites-php, pre-settings-php, db-update, and others) has its own subdirectory containing the executable scripts that should run. ACSF discovers and runs these scripts automatically during the appropriate lifecycle event.
8A Site Owner needs to add a custom domain (example.com) to one of their sites. Which role typically completes the DNS and SSL provisioning step in ACSF?
A.Site Owner only
B.Domain Admin
C.Anonymous user via the public API
D.Platform Admin or Domain Admin
Explanation: Custom domain provisioning in ACSF, including SSL certificate setup, is performed by a Platform Admin or a Domain Admin. Site Owners can request a custom domain, but adding and validating it (including pointing DNS at ACSF and provisioning the SSL certificate) requires the elevated Domain Admin or Platform Admin role. The split exists because mistakes in domain configuration can affect the whole factory's TLS posture.
9Where are individual ACSF site files stored on the platform filesystem?
A.sites/g/files/<site_id>/files
B.sites/default/files
C.var/lib/files
D./mnt/files/<site_id>
Explanation: ACSF stores per-site public files under sites/g/files/<site_id>/files, where <site_id> is the unique numeric identifier ACSF assigns to each site. The sites/g/ path is the convention ACSF uses to namespace per-site directories so that hundreds of sites can coexist on the shared codebase. Private files follow a parallel path under sites/g/files-private/<site_id>/.
10What does the db-update factory-hook do?
A.Runs a SQL backup of every site
B.Executes per-site update scripts (such as drush updb and config import) after a code deployment
C.Replicates the database to a read replica
D.Provisions a brand-new database when a site is created
Explanation: The db-update factory-hook runs once per site after a code deployment, executing per-site update logic such as drush updb (database updates) and drush cim (config import). It is the canonical place to put the post-deploy update steps that every site must run. ACSF iterates over all affected sites and runs db-update for each, which makes it the most important hook for safe rollouts of code that includes schema or config changes.

About the Acquia Site Factory Pro Exam

The Acquia Certified Site Factory Pro exam validates the skills required to operate multi-site Drupal platforms on Acquia Cloud Site Factory (ACSF), including Site Collections, the ACSF Connector module, factory-hooks, site creation and copy, code deployments via Git tags, backup and restore, the ACSF REST API, SAML SSO and User Sync, role management, custom domains and SSL, theme distribution, and platform troubleshooting.

Questions

60 scored questions

Time Limit

75 minutes

Passing Score

65%

Exam Fee

$155 USD (Acquia / Webassessor (Kryterion))

Acquia Site Factory Pro Exam Content Outline

30%

ACSF Administration

Site Owner, Platform Admin, Domain Admin roles, site creation and copy, backup/restore, code deployments via Git tags, User Sync, scheduled tasks, role and team management

25%

ACSF Configuration

Factory Hooks (pre/post-sites-php, pre-settings-php, db-update), shared settings.php, ACSF Connector module, SAML SSO, custom domains and SSL, theme distribution

25%

ACSF Architecture

Site Factory on top of Acquia Cloud, Site Collections, multi-site Drupal, shared codebase, files architecture (sites/g/files), database-per-site, stage vs prod environments, Akamai CDN

20%

ACSF Operations & Troubleshooting

ACSF REST API, sf-toolbelt drush aliases, factory-wide site search, audit logs, IP allowlisting, Varnish/Memcached caching, Stack troubleshooting

How to Pass the Acquia Site Factory Pro Exam

What You Need to Know

  • Passing score: 65%
  • Exam length: 60 questions
  • Time limit: 75 minutes
  • Exam fee: $155 USD

Keys to Passing

  • Complete 500+ practice questions
  • Score 80%+ consistently before scheduling
  • Focus on highest-weighted sections
  • Use our AI tutor for tough concepts

Acquia Site Factory Pro Study Tips from Top Performers

1Memorize the four primary factory-hooks: pre-sites-php, post-sites-php, pre-settings-php, and db-update, and the lifecycle event that triggers each
2Practice the role model: Site Owner (one site), Platform Admin (entire factory), and Domain Admin (custom domain management) and which UI actions each role can perform
3Know the ACSF Connector module's job: it lives on each Drupal site and brokers communication between the site and the Site Factory control plane (SSO, User Sync, REST API)
4Understand code deployments use Git tags pushed to the shared ACSF codebase repo, not per-site branches, and that all sites share one codebase
5Practice the ACSF REST API endpoints for site list, backup, restore, and site copy; these are core operations testers expect you to script

Frequently Asked Questions

What is the Acquia Certified Site Factory Pro pass score and format?

The exam has 60 scenario-based multiple-choice questions in 75 minutes with a 65% passing score. It is delivered through Webassessor (Kryterion) online-proctored.

How does Site Factory Pro differ from Acquia Cloud Pro?

Acquia Cloud Pro covers hosting a single Drupal application on the Acquia Cloud Platform. Site Factory Pro covers Acquia Cloud Site Factory (ACSF), a multi-site management layer on top of Acquia Cloud that uses Site Collections, the ACSF Connector module, factory-hooks, and a shared codebase to operate hundreds of Drupal sites from one platform.

What experience is recommended before taking Site Factory Pro?

Acquia recommends 6-12 months of hands-on experience operating sites on Acquia Cloud Site Factory, including using factory-hooks, the ACSF Connector module, sf-toolbelt drush aliases, and the Site Factory UI for site creation, copy, backup, and code deployments.

How long should I study?

Most candidates study 4-6 weeks, investing 30-60 hours. Lab time inside an ACSF sandbox is the highest-yield preparation, especially for factory-hooks, Connector configuration, and the ACSF REST API.

Which factory-hooks are tested most heavily?

pre-sites-php and post-sites-php (modifying sites.php during site creation), pre-settings-php (injecting settings before Drupal bootstrap), and db-update (running per-site updates after a deploy) appear repeatedly. Know which hook fires for which lifecycle event.