Acquia Updated Drupal-Site-Builder Exam Questions and Answers by ilyas

In Drupal 10 and Drupal 11 Views, the correct place to add a CSS class to each rendered row is the Format → Settings → Row class option. Drupal core’s Views API shows that style plugins can provide a Row class text field, and when the display uses fields, this option explicitly supports field tokens . The documentation in core states: “You may use field tokens … for all fields.” That means you can add the Manufacturer field to the View and use its token in the Row class setting so each row gets a class derived from that field’s value. Drupal then token-replaces the value for each row and sanitizes it into a valid CSS identifier.

The other options do not match how Drupal Views handles per-row CSS classes. Attachments do not assign row classes to the main display, a separate custom field is not required for this built-in capability, and group-by options are for grouping results rather than applying row-level CSS classes. So the Drupal-native, documented method is to put the Manufacturer field token directly into the Row class setting in the display’s Format settings .

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