Drupal-Site-Builder Sample Questions Answers

The most effective and Drupal-recommended way to prevent automated (bot-driven) user registrations is to implement a challenge-response mechanism such as CAPTCHA. In Drupal 10 and Drupal 11, this is achieved using the CAPTCHA module (often paired with reCAPTCHA), which integrates directly into forms like user registration. By enabling a CAPTCHA field on the registration form, bots are prevented from submitting automated requests because they cannot solve the challenge, while legitimate users can proceed normally.

Drupal’s security best practices emphasize mitigating automated abuse at the form level rather than relying solely on post-registration controls. Option A (email verification) still allows bots to create accounts and flood the system, even if they cannot activate them. Option C (hiding login) does not affect registration endpoints and provides no real protection. Option D (restricting registration to administrators only) eliminates self-registration entirely, which may not meet business requirements and is not a balanced solution.

Therefore, enabling CAPTCHA directly addresses the root cause—automated submissions—making it the most appropriate and scalable solution according to Drupal security guidelines.

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

For a corporate site where public visitors do not need self-service accounts, the correct Drupal site-building solution is to disable visitor registration. Drupal’s official User Guide for Configuring User Account Settings says to go to Configuration > People > Account settings and, under Registration and cancellation , select “Administrators only” as the people with permission to register user accounts. This turns off public account creation and is the standard Drupal method for stopping spam registrations on sites that do not need open sign-up.

The other choices do not match Drupal’s documented account-management approach. Option B still allows visitors to create accounts, so it does not prevent spam registrations; a password strength indicator is unrelated to blocking bot sign-ups. Option A would protect the entire site at the web-server level, which is not the intended Drupal account-registration setting and would block all anonymous access, contradicting the site’s normal public use. Option D refers to unrelated contact-form behavior and does not control account creation. Drupal’s account settings documentation specifically identifies “Administrators only” as the way to stop visitor registration, making C the verified answer.

In Drupal 10 and Drupal 11, access to the site during maintenance mode is controlled through a specific permission rather than a configuration setting tied directly to roles on the maintenance mode page. The correct approach is to create a role and grant it the permission “Use the site in maintenance mode.” Users assigned this role will be able to bypass the maintenance mode restriction and access the site while it is offline for regular visitors.

Option C reflects this exact mechanism and aligns with Drupal core’s permission-based access control system. Drupal uses roles and permissions extensively to manage access, and maintenance mode is no exception.

Option A is incorrect because access is not limited strictly to administrators; it depends on permissions. Option B is incorrect because the Maintenance mode configuration page does not provide role selection for access—this is a common misconception. Option D is also incorrect because granting “Administer site” gives excessive privileges and is not required for maintenance mode access; it violates the principle of least privilege.

Therefore, assigning the “Use the site in maintenance mode” permission is the correct, secure, and Drupal-recommended solution.

The correct answer is D . In Drupal 10 and Drupal 11, retaining past versions of content is handled through node revisions . Drupal’s official documentation explains that revisions are controlled at the content type level, and the relevant setting is the “Create new revision” checkbox in the content type configuration. When this option is enabled, Drupal creates a new revision by default whenever content of that type is updated, allowing editors and administrators to retain and review previous versions of the content.

The other options are not correct according to Drupal core documentation. Content Moderation is related to editorial workflows and depends on revisions, but it is not required just to keep past versions of content. There is also no core module called Content Revisions for enabling this basic feature, and “Enable content history” is not the Drupal node setting used for revision retention. Drupal’s API documentation for NodeType::$new_revision and setNewRevision() confirms that the content type stores whether new revisions should be created by default. The Drupal site-building documentation also notes that new content types, as well as standard Article and Page types, use the Create new revision setting for revision behavior.

I understand you want the next one in the same exact format, verified against Drupal 10/11 site-building documentation. Here it is.

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 .

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.

Drupal 10 and Drupal 11 provide multiple ways to control how content is displayed without altering the underlying data. The requirement here is to show only selected fields (image, title, cuisine) in a listing, while keeping the full description available on the detail page.

Option A is correct because Views allows you to display content as fields , meaning you can explicitly choose which fields to show. This is a core feature of the Views module and is commonly used for listing pages.

Option C is also correct because Drupal supports view modes (like Teaser and Full). The documentation explains that you can configure the Teaser view mode to show only selected fields. Then, in Views, you can display content using that view mode. This approach is reusable and aligns with Drupal’s display system.

Option B is incorrect because creating a duplicate content type is unnecessary and violates content modeling best practices. Option D is incorrect because hiding fields with CSS does not remove them from the rendered output and is not a proper Drupal solution.

Thus, using Views fields or Teaser view mode are the correct, documented approaches.

Drupal 10 and Drupal 11 provide the Layout Builder module in core, which allows site builders and content editors to control how fields are displayed. There are two levels of control: content type–level layouts and per-content (per-node) layout overrides .

Option A only allows rearranging fields globally for all nodes of that content type, which does not meet the requirement of having different layouts per job posting. Option B involves theming and template overrides, which require developer intervention and are not intended for content editors or HR staff.

Option C enables Layout Builder but only at the content type level, meaning all job openings would share the same layout. This still does not satisfy the requirement for different arrangements per node.

Option D is correct because enabling Layout Builder and allowing each content item to have its layout customized activates the “Allow each content item to have its layout customized” setting. Drupal documentation explains that this allows individual nodes to override the default layout, giving flexibility to rearrange fields differently for each job opening while still using a structured, UI-based approach.

Thus, Layout Builder with per-node customization is the correct solution.

Drupal 10 and Drupal 11 include the Contact module in core, which allows administrators to create multiple contact form types . Each contact form can have its own configuration, including recipients and email notifications . According to Drupal documentation, you can create custom contact forms (e.g., RSVP) and configure them to send emails to specified recipients when a user submits the form.

Option A is correct because creating a dedicated RSVP contact form allows you to configure email notifications to both the attendee (via auto-reply) and the site administrator. This approach uses Drupal core functionality and is the recommended way to handle simple form submissions with email notifications.

Option B is incorrect because content types are used for structured content, not form submissions with email handling. Option C is not ideal because the site-wide contact form is meant for general communication and does not provide flexibility for RSVP-specific workflows. Option D is unnecessary since Drupal core already provides the required functionality.

Thus, the best and documented solution is to create a custom contact form and configure its email settings, making A correct.

Drupal distinguishes between interface text and configuration text . The built-in labels and other text that come from Drupal core, modules, and themes are handled by the Interface Translation system, and Drupal can download those translations for added languages. The Drupal User Guide explains that this built-in text is typically translated by downloading available translations rather than translating it yourself.

By contrast, field labels are configuration. Drupal’s multilingual documentation says that configuration text includes items such as labels for fields in your content types , and the Configuration Translation module provides the interface to translate that configuration into other languages. It also specifically lists Content fields as translatable configuration elements. That means field labels you created yourself in Spanish are not automatically translated into French just because French is added; they must be translated through configuration translation.

So, when French is added, Drupal can automatically provide translations for built-in field/interface text where translations exist, but custom field configuration labels still require manual translation . Therefore, option C is the correct answer.