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

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’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, favicon settings are managed at the theme level , not through general site configuration. The official Drupal theming documentation explains that each theme has its own configurable settings, including the ability to upload or replace the site’s favicon.

To change the favicon, you navigate to Appearance → Settings (or specifically the active theme’s settings page), where you will find an option to upload a custom favicon or use the default. This allows you to replace the default Drupal icon (Druplicon) with your organization’s icon.

Option A is incorrect because the Site branding block controls elements like the logo and site name, not the favicon. Option C is incorrect because Basic Site Settings does not manage favicon configuration in modern Drupal versions. Option D is unnecessary and incorrect, as CSS is not used to change favicons.

Therefore, the correct and documented method is to update the favicon through the theme settings in the Appearance section , making option B correct.

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 .

Drupal handles date and time display through regional settings and user account timezone preferences , not through content type configuration. The correct solutions are therefore A and C . Enabling “Users may set their own time zone” allows authenticated users to choose their own timezone in their user account settings, so dates such as content publication times are displayed according to each user’s local timezone. This is the most accurate solution when users may come from different regions.

Changing the default timezone to that of your primary audience, in this case France, is also correct. Drupal uses the site default timezone for users who have not set a personal timezone, and for anonymous visitors. This makes displayed times more appropriate for the majority of site visitors.

Option B is incorrect because Drupal does not provide timezone handling at the content type level. Timezone behavior is managed globally and per user, not per content type. Option D is also incorrect because setting the default country affects address-related defaults and locale-related behavior, but it does not control how Drupal displays timestamps. Therefore, the verified answers are A and C .