Drupal-Site-Builder Dumps with Practice Exam Questions Answers

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 (Standard installation profile), several roles are created automatically to support common editorial workflows. These include Authenticated user , Content editor , and Administrator .

Authenticated user is a core default role in all Drupal installations. It represents any logged-in user and is always present.

Content editor is provided by the Standard installation profile as part of Drupal’s out-of-the-box editorial workflow, allowing users to create and manage content.

Administrator is also included and has full permissions to manage the entire site.

Options A (Site builder) and C (Publisher) are not default roles created by Drupal core or the Standard profile. While such roles can be created manually or may appear in specific distributions, they are not included by default.

Drupal’s documentation for installation profiles confirms that the Standard profile provides a pre-configured editorial setup, including roles like Content editor, in addition to the core Authenticated user and Administrator roles.

Therefore, the correct answers are B, D, and E .

In Drupal 10 and Drupal 11, content that appears in the sidebar across all pages is typically implemented as a custom block placed in a theme region via the Block Layout system. Drupal documentation explains that reusable content like contact information is best managed through custom blocks , which can be edited centrally and automatically update everywhere they are placed.

Option A is correct because the proper way to update such content is to go to Structure → Block layout → Custom block library , locate the block, and edit it. This ensures the change is reflected globally wherever the block is used.

Option C is also correct because Drupal provides contextual links (the pencil icon) that allow administrators to directly edit blocks from the front end. This is a standard and documented shortcut for editing block content.

Option B is incorrect because Layout Builder is not mentioned and is not required here. Option D is incorrect because editing individual pages would not update a shared sidebar block and would be inefficient and incorrect.

Thus, the correct Drupal site-building approaches are editing the custom block via the block library or using contextual links, making A and C correct.

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.

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.