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

Drupal core search does not index newly created or updated content immediately in the default workflow. According to the official Drupal core Search module overview , content actions such as creating, editing, or deleting content automatically mark the affected content items for indexing or reindexing at the next cron run . Until cron runs, the new or changed content is not updated in the search index, so a newly created article may not appear in search results even though search is otherwise functioning correctly.

This makes option C the correct answer. The other options do not match Drupal core behavior. There is no normal site-building step where you configure core search to “recognize” a specific term, and Drupal does not provide an “Add to search index” checkbox when creating an article in core search. Also, while contributed search solutions exist, the question states that Drupal core search is already working correctly, so the missing result is best explained by indexing timing, not by a flaw requiring another module. Drupal’s search documentation is explicit that cron is responsible for updating the index after content changes.

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, blocks are placed and managed through the Block Layout system available at Structure → Block layout . Each theme defines regions such as Sidebar, Footer, Header, etc., and administrators can assign blocks to these regions.

Since the “Social share” buttons are implemented as a custom block , the correct approach is to reposition the block using the Block Layout admin interface . This interface allows site builders to move blocks between regions either by dragging or by editing the block’s region setting. This matches Drupal’s documented site-building practice for managing block placement.

Option A is incorrect because Manage display is used for configuring how fields are displayed on entities, not for block placement. Option C is incorrect because the Appearance page controls themes, not individual block placement. Option D is unnecessary because Layout Builder is used for per-content or per-entity layouts, not for globally placed blocks like a social share block.

Therefore, the simplest and correct solution is to move the block via the Block Layout page, making option B correct.

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.

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, 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.

Drupal’s recommended solution for reusable images with their own metadata is to use Media entities , not ordinary image fields on content. Core documentation and issue work around Media in Drupal explain that moving from regular image fields to media image fields is what enables reuse of the same image asset across multiple pieces of content.

That means the description should live on the media item itself , together with the image, and content types should reference that media item through a media reference field . Drupal field documentation also confirms that fields can be attached to entities and reused appropriately through references. So creating a new media type with an image field plus a description field is valid, and adding a description field to an existing Image media type is also valid. Both approaches satisfy the requirement that the image and its description stay together and can be reused elsewhere.

Option B is incorrect because Drupal core already provides Media for this use case. Option C is not the best content model because a content type represents publishable content, while reusable images-with-metadata are better modeled as Media assets.

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.

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.