Acquia Drupal-Site-Builder Acquia Certified Drupal Site Builder Exam for Drupal 10, 11 Exam Practice Test

Drupal 10 and Drupal 11 include the Contact module in core, which allows administrators to create multiple contact form types . Each contact form can have its own configuration, including recipients and email notifications . According to Drupal documentation, you can create custom contact forms (e.g., RSVP) and configure them to send emails to specified recipients when a user submits the form.

Option A is correct because creating a dedicated RSVP contact form allows you to configure email notifications to both the attendee (via auto-reply) and the site administrator. This approach uses Drupal core functionality and is the recommended way to handle simple form submissions with email notifications.

Option B is incorrect because content types are used for structured content, not form submissions with email handling. Option C is not ideal because the site-wide contact form is meant for general communication and does not provide flexibility for RSVP-specific workflows. Option D is unnecessary since Drupal core already provides the required functionality.

Thus, the best and documented solution is to create a custom contact form and configure its email settings, making A correct.

Because all three content types use a Media reference field that allows the Image media type , the actual uploaded file restrictions are controlled by the source field on the Media type , not by each content type’s reference field. In Drupal, the Image media type contains an image field as its source field, and image/file fields have settings such as allowed file extensions . Drupal’s Image module documentation states that image fields can be configured with settings including allowed extensions .

Therefore, to block GIF uploads everywhere this Image media type is used, you edit the Image media type , go to Manage fields , edit its image source field , and remove gif from the allowed extensions. Since all three content types reference that same media type, the restriction applies consistently across all of them. This is the most efficient and Drupal-native solution.

Option A is incorrect because the media reference field on a content type controls which media types may be referenced, not which file extensions the media type’s source field accepts. Option C concerns form widget display, not file validation. Option D is too general; the actual extension restriction lives on the image field settings within the media type.

Drupal distinguishes between interface text and configuration text . The built-in labels and other text that come from Drupal core, modules, and themes are handled by the Interface Translation system, and Drupal can download those translations for added languages. The Drupal User Guide explains that this built-in text is typically translated by downloading available translations rather than translating it yourself.

By contrast, field labels are configuration. Drupal’s multilingual documentation says that configuration text includes items such as labels for fields in your content types , and the Configuration Translation module provides the interface to translate that configuration into other languages. It also specifically lists Content fields as translatable configuration elements. That means field labels you created yourself in Spanish are not automatically translated into French just because French is added; they must be translated through configuration translation.

So, when French is added, Drupal can automatically provide translations for built-in field/interface text where translations exist, but custom field configuration labels still require manual translation . Therefore, option C is the correct answer.

Drupal 10 and Drupal 11 documentation strongly recommend using community-supported channels for troubleshooting contributed modules. The primary and most appropriate place to seek help is the module’s issue queue on drupal.org , where users can search for existing issues, report bugs, and ask questions. This ensures transparency, allows maintainers and contributors to track problems, and benefits the wider community. Therefore, option A is correct.

Additionally, Drupal has active community communication platforms such as Drupal Slack and IRC channels (like #drupal-support), where developers and site builders collaborate and provide real-time assistance. These are officially recognized community support channels, making option B correct.

Option C is incorrect because Drupal project pages do not use general comments for support; instead, all discussions should happen in the issue queue. Option D is discouraged because directly emailing maintainers bypasses the public support process and is not aligned with Drupal community best practices.

Thus, the correct and recommended ways to find help are using the issue queue and community support channels.

In Drupal 10 and Drupal 11, access to the site during maintenance mode is controlled through a specific permission rather than a configuration setting tied directly to roles on the maintenance mode page. The correct approach is to create a role and grant it the permission “Use the site in maintenance mode.” Users assigned this role will be able to bypass the maintenance mode restriction and access the site while it is offline for regular visitors.

Option C reflects this exact mechanism and aligns with Drupal core’s permission-based access control system. Drupal uses roles and permissions extensively to manage access, and maintenance mode is no exception.

Option A is incorrect because access is not limited strictly to administrators; it depends on permissions. Option B is incorrect because the Maintenance mode configuration page does not provide role selection for access—this is a common misconception. Option D is also incorrect because granting “Administer site” gives excessive privileges and is not required for maintenance mode access; it violates the principle of least privilege.

Therefore, assigning the “Use the site in maintenance mode” permission is the correct, secure, and Drupal-recommended solution.

In Drupal’s official documentation, headless Drupal is described as decoupled Drupal . The documentation explains that decoupled, or headless, Drupal separates the backend content management part of Drupal from the frontend presentation layer . In this architecture, Drupal is used as a content repository and content API, while the frontend can be built with other technologies such as JavaScript frameworks or consumed by other clients. This directly supports option C

Drupal documentation also explains that this architecture allows Drupal content to be exposed to other systems and applications through APIs such as JSON:API or REST. That means Drupal can provide content to websites, mobile apps, kiosks, or other digital channels, which matches option B . The purpose of headless Drupal is therefore not automatic updates or automatic publishing, so options A and D are not correct.

So, according to Drupal 10 and Drupal 11 documentation, the correct understanding is that headless Drupal means decoupled Drupal and involves exposing Drupal-managed content to external systems or applications through APIs .

Drupal’s issue queue guidelines clearly distinguish between different issue types. A Bug Report is used when existing functionality is broken or not working as intended. In this case, the module is functioning correctly—it simply does not provide a UI—so option A is incorrect.

A Feature Request is the correct issue type when asking for new functionality or enhancements to an existing module. Requesting a web-based UI for a module that currently only provides Drush commands is a classic example of a feature enhancement, making option C correct.

Option B (“Plan”) is typically used for outlining larger initiatives or coordinated development efforts, not for requesting a specific feature. Option D is incorrect because Drupal issue queue best practices emphasize clear, descriptive, and professional issue titles , avoiding urgency or misleading wording like “Module Broken!!!” when it is not actually broken.

Drupal.org documentation encourages contributors to categorize issues properly and write clear, concise summaries so maintainers and the community can effectively review and respond. Therefore, submitting a Feature Request with a clear subject line is the correct and recommended approach.

Drupal’s official security guidance for the super user account ( user 1 ) specifically recommends that administrators do not name the first account “admin” or something obvious . The reason is straightforward: obvious usernames make brute-force and credential-guessing attacks easier, because attackers already know half of the login credentials they need to target. Drupal’s administration and security documentation also recommends limiting direct use of user 1 and protecting it carefully because it is a uniquely powerful account.

That makes option D the correct answer. The other options do not match Drupal’s documented best practices. There is no Drupal security rule about “members of the Drupal community in good standing” being allowed to use user 1. Canceling the user 1 account is not the recommended solution for this situation, and removing the Administrator role from user 1 would not make the account anonymous; in Drupal, user 1 is a special account with superuser behavior that is handled separately from ordinary role assignment. Drupal’s own guidance emphasizes safer naming and tighter handling of the account, not these alternative actions.

In Drupal 10 and Drupal 11, each content item (node) can only have one menu link created through its Menu settings . Drupal documentation explains that the Menu settings section allows you to place a node in a menu, but only as a single menu item . Therefore, you cannot create two menu links for the same node directly from the node edit form, which makes option D incorrect.

The correct approach is to create one menu link via the node’s Menu settings (placing it under “Products”), and then manually add an additional menu link in the Menu administration (Structure → Menus → Main navigation) that points to the same node but is placed under “What’s New.” This matches option A . After the promotion, the temporary menu link can be removed.

Option B is incorrect because duplicating content creates unnecessary redundancy and breaks content management best practices. Option C is incorrect because Drupal core does not provide a built-in “menu link expiration” feature.

Thus, Drupal’s recommended method is to create one menu link via the node and another manually via the menu UI, making A the correct answer.

In Drupal 10 and Drupal 11, a View is stored as configuration , and Drupal provides a built-in Configuration Management system to move configuration between environments. According to the official Drupal User Guide, when you want to move a single configuration item (such as a View), the recommended approach is to use the Single Export and Single Import functionality available in the admin interface.

On the development site, you navigate to Configuration → Development → Configuration synchronization → Export → Single item , select View , and copy the YAML configuration. Then, on the production site, you go to Import → Single item and paste the configuration to import it.

Option A refers to full configuration synchronization, which is typically used for complete site configuration deployment, not for a single View. Option B is incorrect because Backup and Migrate is meant for database backups, not configuration transfer. Option C is incorrect because Drupal provides a UI-based method for this task.

Thus, the correct and documented approach is partial export/import using the single configuration option, making D the correct answer.

In Drupal 10 and Drupal 11, Views contextual filters are used to dynamically filter content based on values passed through the URL. When filtering content by taxonomy (such as Landmarks), you configure a contextual filter using the taxonomy term field associated with the content type.

To pass a value like a term name in the URL , you must configure the contextual filter to accept term identifiers such as term ID or term name . Drupal Views allows validation and transformation of contextual input, including using the taxonomy term name via settings like “Provide default value” or “Specify validation criteria.” This matches option B.

Option A is incorrect because exposed filters rely on user input via UI forms, not URL path arguments. Option C is unnecessary duplication and not aligned with best practices. Option D is not required because taxonomy reference fields already provide the necessary relationship internally for filtering; explicitly adding a relationship is only needed in more complex multi-entity scenarios.

Therefore, the correct approach is to use a contextual filter configured to accept the taxonomy term (including term name) via the URL, making option B correct.

The correct answer is D . In Drupal 10 and Drupal 11, retaining past versions of content is handled through node revisions . Drupal’s official documentation explains that revisions are controlled at the content type level, and the relevant setting is the “Create new revision” checkbox in the content type configuration. When this option is enabled, Drupal creates a new revision by default whenever content of that type is updated, allowing editors and administrators to retain and review previous versions of the content.

The other options are not correct according to Drupal core documentation. Content Moderation is related to editorial workflows and depends on revisions, but it is not required just to keep past versions of content. There is also no core module called Content Revisions for enabling this basic feature, and “Enable content history” is not the Drupal node setting used for revision retention. Drupal’s API documentation for NodeType::$new_revision and setNewRevision() confirms that the content type stores whether new revisions should be created by default. The Drupal site-building documentation also notes that new content types, as well as standard Article and Page types, use the Create new revision setting for revision behavior.

I understand you want the next one in the same exact format, verified against Drupal 10/11 site-building documentation. Here it is.

Drupal 10 and Drupal 11 are flexible because they provide major site-building capabilities through configuration and core modules, instead of requiring everything to be custom-coded. Drupal supports headless/decoupled use cases out of the box through core web services such as JSON:API , which Drupal documentation describes as a standard way to expose site content for decoupled applications. That makes A correct.

Drupal also provides strong content modeling through entity types and fields, and it supports listing and displaying content through the Views UI . The User Guide and core documentation explain that site builders can define structured content types and then create listings, pages, blocks, sorting, and filtering through Views without writing custom code. That makes B correct.

Drupal additionally ships with a rich administrative interface for installing modules, managing themes, creating content types, editing fields, configuring permissions, and administering content. This is one of the platform’s core strengths compared with a purely custom-built system, so E is correct.

Options C and D are not correct. Drupal.org provides contributed projects, but not an online store for buying modules and themes, and Drupal does not present direct database-column renaming as a normal UI-based site-building feature.

In Drupal 10 and Drupal 11, user accounts are fieldable entities , which means you can add custom fields directly to user accounts through the administrative UI. Drupal’s field documentation explains that fields can be added to various entity types, including users , not just content types. So if you want each user to choose a favorite weapon, the correct site-building approach is to add a field such as Favorite weapon to the User entity using the Manage fields interface for user accounts. This makes option A correct.

This approach is also flexible. The field could be a plain list, an entity reference, or a taxonomy term reference if the site needs a controlled list of weapons. The important point is that the selection belongs to the user profile/account , because the requirement is about storing a preference for each user.

The other options are not the correct primary solution. Option B creates taxonomy terms but does not by itself provide the user-selection field. Option C uses content and Views instead of storing a value on user accounts. Option D is incorrect because Drupal users are not modeled as a content type. Therefore, adding a field to user accounts is the proper Drupal-native solution.

In Drupal 10 and Drupal 11, security updates for contributed modules must be applied promptly to protect the site from known vulnerabilities. Drupal core provides a built-in Update Manager module that notifies administrators when updates, especially security releases, are available. However, Drupal does not automatically install updates , including during cron runs, so option C is incorrect.

The correct process, as documented in Drupal’s official update procedures, involves downloading the latest recommended release of the module (typically via Composer or manual replacement), and then running database updates using the /update.php script or drush updb . This ensures that any schema changes required by the new version are properly applied.

Option B is incorrect because uninstalling a module is unnecessary and can lead to data loss or configuration issues. Option A is clearly wrong, as ignoring security updates exposes the site to risks.

Therefore, the proper and documented approach is to update the module codebase and run update.php to finalize the update process, making option D the correct answer.