Drupal-Site-Builder Acquia Certified Drupal Site Builder Exam for Drupal 10, 11 Questions and Answers

Drupal 10 and Drupal 11 provide block visibility conditions that allow administrators to control where blocks appear. According to Drupal’s block system documentation, when placing a block through Structure → Block layout , you can configure visibility based on content types, pages, roles, or request paths .

To meet the requirement of showing the "Recent content" block only on Article pages, the correct approach is to place the block in the Sidebar region and configure its visibility condition to Content types → Article . This ensures the block is displayed only when viewing nodes of the Article content type and hidden elsewhere.

Option A is incorrect because using CSS to hide blocks is not a proper Drupal configuration and still renders the block unnecessarily. Options B and C are invalid because Drupal does not provide such settings in content type or site branding configurations.

Thus, using block visibility settings tied to the Article content type is the correct and recommended method in Drupal site building.

In Drupal 10 and Drupal 11, the administrative Comments listing is provided by the core comment View. In core’s default views.view.comment configuration, the comments administration display uses the table style, includes the entity_id field labeled “Posted in” , and that column is present in the table configuration. However, core sets that column’s table option to sortable: false , while other columns such as Subject, Author, and Updated are sortable. That is why moderators cannot sort the approval page by the content item the comment belongs to, even though the field is already there.

Because the existing approval page already uses a View, the simplest solution is to edit that View and enable sorting for the Entity ID / Posted in column in the table settings. Creating a brand-new View would work, but it is not the simplest option because it duplicates an existing administrative display. The other options do not address the actual issue with the current moderation screen. Drupal’s content administration documentation also confirms that comments are managed from the Comments administration page, making improvement of that interface the most appropriate site-building solution.

In Drupal, a comment field can only use comment types that are configured for the same target entity type as the entity you are attaching comments to. When you add a comment field to a Content type (node), Drupal expects a comment type whose Target entity type is Content . If the new comment type was created with another target entity type, such as custom block or user, it will not appear as a selectable option when adding that comment field to a content type. This is consistent with Drupal core’s comment architecture and field behavior.

The other choices do not match Drupal’s documented behavior. “Allow comments” is not a separate prerequisite checkbox that controls whether a comment type appears; instead, comments are enabled by adding a comment field to the content type. Drupal documentation for administering comment settings confirms that comment capability is added from Manage fields by adding or reusing a comment field. There is also no documented requirement that custom comment types work only on default content types, and cache clearing is not described as the fix for this selection issue.

Drupal 10 and Drupal 11 let you control block display through visibility conditions on the block configuration form. Drupal’s block management documentation explains that a block’s visibility can depend on page-specific visibility settings and also on user role conditions. For page visibility, Drupal specifically notes that the front page is an exception and must be entered as < front > . To show a block only on the homepage, you add < front > in the Pages visibility settings and choose “Show for the listed pages.”

To limit the block to a specific audience, you use the Roles visibility condition and select the exact role that should see the block. In this case, that is Premium customer , not the broader Authenticated user role, because selecting Authenticated user would show the block to all logged-in users who have that role, not just premium customers. Drupal core’s block form API also confirms that block visibility is built through configurable visibility conditions in the block UI.

So the correct combination is:

A for the role restriction, and B for the front-page-only restriction.

In Drupal 10 and Drupal 11, the correct way to display resized images (such as thumbnails) is by using Image Styles . Image styles allow Drupal to generate derivative images with specific dimensions (e.g., thumbnail size) and serve those instead of the original full-sized image. This significantly improves performance because smaller image files are loaded, reducing page load time and bandwidth usage.

Drupal’s Image module documentation explains that image styles can apply effects such as scaling, cropping, and resizing, and are typically used in Views or field display settings to ensure appropriately sized images are rendered.

Options C and D (JavaScript and CSS resizing) only change how images appear visually but still load the full-size image , which does not improve performance. Option A refers to performance settings but does not specifically handle image resizing.

Therefore, using an image style is the correct, recommended, and documented approach for optimizing image display and improving site performance.

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.

Drupal core provides a specific setting for whether node add/edit forms should use the administration theme. On the Appearance page, this is the checkbox labeled “Use the administration theme when editing or creating content” . When that setting is enabled, content creation and editing routes are treated as admin-theme routes; when it is disabled, those forms use the site’s default front-end theme instead, while the rest of the administration area can still use the admin theme such as Claro. This behavior is implemented in core through the node.settings configuration value use_admin_theme and the node route subscriber that marks node operation routes as admin routes only when that setting is turned on.

That makes option A correct. Option B would not solve the requirement, because setting the admin theme as the default theme would affect the whole site’s front-end presentation. Options C and D are incorrect because Drupal does not use a role permission like “View Admin Theme” to control this behavior for node edit pages. The documented control for this requirement is the Appearance-page checkbox tied to node.settings.use_admin_theme .

Drupal 10 introduced several important enhancements and modernizations in core, focusing on improving developer experience, site building, and front-end capabilities. One of the most significant updates is the replacement of CKEditor 4 with CKEditor 5 , which provides a modern editing experience and better extensibility.

Drupal 10 also includes the Starterkit theme generator , which replaces older base themes and allows developers to create custom themes more cleanly and maintainably. Additionally, improvements were made to Layout Builder , enhancing usability and flexibility for managing layouts without requiring custom code.

Drupal continues to support decoupled/Headless architectures using built-in APIs like JSON:API, and improvements in this area are reflected in Drupal 10’s capabilities.

The other options list features typically provided by contributed modules , not Drupal core. For example, Webforms, SEO tools, social sharing, and flags are not part of Drupal core and must be added separately.

Thus, option A correctly represents features and improvements included in Drupal 10 core.

In Drupal 10 and Drupal 11, menus can be displayed as blocks and configured to show specific levels of the menu hierarchy. The “Main navigation” block includes settings such as “Starting level” (or initial visibility level) and “Maximum number of levels to display.” These settings allow site builders to control which part of the menu tree is visible in a given region.

To display only the child pages (submenu items) when a user is on a child page, you need to configure the block to start displaying from level 2 , which corresponds to the submenu under the current top-level section. This ensures that only relevant sibling pages within the same section are shown in the sidebar, improving usability and navigation.

Option B (level 1) would still show top-level menu items, not just the submenu. Option A is not recommended because using CSS to hide elements does not follow Drupal’s configuration best practices. Option D is unnecessary and inefficient, as Drupal’s menu system already supports hierarchical display without creating duplicate menus.

Thus, configuring the menu block with an initial visibility level of 2 is the correct and recommended approach.

In Drupal 10 and Drupal 11, a module can appear on the Extend page but still have its checkbox unavailable when Drupal determines that its requirements are not met. One of the most common and documented reasons is missing dependencies . Drupal modules declare dependencies in their .info.yml file, and if one or more required modules are not present or enabled, Drupal prevents installation until those dependencies are satisfied. Drupal’s module documentation specifically notes that when a module is listed on admin/modules but its checkbox is disabled, you should verify compatibility and requirements declared in the module metadata.

Option D fits Drupal’s standard dependency behavior. This is also consistent with Drupal community documentation explaining that if you cannot check a module or feature on the module listing page, it is most likely because required dependent modules are missing, and unmet dependencies should be checked first.

The other options are not the correct explanation here. modules/contrib is a valid and standard location for contributed modules, and downloading a module outside the Drupal UI does not itself disable installation. A missing permission would typically affect access to the page or action availability, but the classic reason for a disabled module checkbox on the Extend page is unmet dependencies.

The main security risk in this scenario is the unrestricted file upload field exposed to anonymous users. Drupal’s file API documentation explains that file uploads must use validation and a defined list of allowed extensions. Core specifically notes that uploading arbitrary files is dangerous and that validation is necessary. The Drupal file API also states that using a managed file field with defined allowed extensions helps sanitize filenames, validate files, and block insecure extensions by default. Without those restrictions, anonymous visitors could upload unsafe files, including malicious or infected files, to the server.

Option A is too broad, because anonymous users can legitimately access public forms on Drupal sites. The issue is not public access by itself, but public access combined with missing validation and upload restrictions . Option C describes a possible performance problem, not the most important security threat identified by Drupal’s documentation. Option D is clearly incorrect because Drupal’s security guidance stresses protecting public forms and validating uploads carefully, especially on forms exposed to anonymous users.

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.