Pass the Acquia Drupal 10/11 Drupal-Site-Builder Questions and answers with Dumpstech

Drupal controls HTML markup through text formats and filters . The official User Guide explains that text formats such as Basic HTML and Full HTML determine which tags are allowed, and these formats exist specifically to protect the site from unsafe markup such as XSS. Because of that, if editors need to use < div > tags, one valid solution is to configure the content so it can use the Full HTML text format, which is the most permissive core format. Drupal also supports restricting or allowing which text formats are available on a formatted text field, including the Body field.

Another valid solution is to edit the Basic HTML text format and add < div > to the list of allowed HTML tags. Drupal’s text format configuration page explicitly allows administrators to change the Allowed HTML tags for Basic HTML. That makes option C correct as well. Option B is incorrect because Drupal does not use a permission named “Use advanced HTML”; permissions are tied to specific text formats. Option D is incorrect because theme settings do not control which tags are allowed in editor input.

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.

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

Drupal’s Comment module supports creating different comment types and attaching them to content entities. The official Comment module documentation states that Drupal can create new comment types that can be attached to content entities, and the detailed comment documentation explains that when you create a comment type and choose the target entity type as Content , that comment type becomes available when adding a comment field to a content type.

Drupal’s field documentation also explains that fields on comments are defined at the content-type level , on the Comment fields tab of the content type edit page. When you add a field for comments, each comment on content items of that type gets that field. Drupal even gives an example of adding a field to comments for one content type but not another, which matches this requirement exactly.

So the right solution is to create a new comment type for Places comments, add a Country field to that comment type, and then use that comment type on the Places content type only. The other options either store the data in the wrong place or do not make it specific to comments on Places.

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 .

Because all three content types use a Media reference field that allows the Image media type , the actual uploaded file restrictions are controlled by the source field on the Media type , not by each content type’s reference field. In Drupal, the Image media type contains an image field as its source field, and image/file fields have settings such as allowed file extensions . Drupal’s Image module documentation states that image fields can be configured with settings including allowed extensions .

Therefore, to block GIF uploads everywhere this Image media type is used, you edit the Image media type , go to Manage fields , edit its image source field , and remove gif from the allowed extensions. Since all three content types reference that same media type, the restriction applies consistently across all of them. This is the most efficient and Drupal-native solution.

Option A is incorrect because the media reference field on a content type controls which media types may be referenced, not which file extensions the media type’s source field accepts. Option C concerns form widget display, not file validation. Option D is too general; the actual extension restriction lives on the image field settings within the media type.

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 .

Drupal 10 introduced several important enhancements and modernizations in core, focusing on improving developer experience, site building, and front-end capabilities. One of the most significant updates is the replacement of CKEditor 4 with CKEditor 5 , which provides a modern editing experience and better extensibility.

Drupal 10 also includes the Starterkit theme generator , which replaces older base themes and allows developers to create custom themes more cleanly and maintainably. Additionally, improvements were made to Layout Builder , enhancing usability and flexibility for managing layouts without requiring custom code.

Drupal continues to support decoupled/Headless architectures using built-in APIs like JSON:API, and improvements in this area are reflected in Drupal 10’s capabilities.

The other options list features typically provided by contributed modules , not Drupal core. For example, Webforms, SEO tools, social sharing, and flags are not part of Drupal core and must be added separately.

Thus, option A correctly represents features and improvements included in Drupal 10 core.

Drupal’s configuration management system is specifically designed to move site configuration —such as content types, fields, vocabularies, and Views—between environments by exporting configuration to files and then importing it elsewhere. Drupal documentation explicitly describes configuration as the administrative settings that determine how the site functions, and it lists fields and views as examples of configuration.

That makes option D the correct workflow: build the new fields and View on a development copy of the site, export the configuration to code, deploy that code to staging, import it for QA review, and then repeat the import in production after approval. This preserves live editorial activity such as comments , because comments are site content , not configuration, and configuration deployment avoids overwriting production content with a copied database.

Option A is risky because copying the staging database back to production could overwrite live comments and other newly created production content. Option B is false because staging and production do not automatically share configuration through one database in a normal deployment workflow. Option C is inferior because configuration should be created from a development copy of the actual site, where the existing modules, schema, and site setup already match the target environments.