Accurate Hot Selling Drupal-Site-Builder Exam Dumps 2026 Newly Released
Get 100% Authentic Acquia Drupal-Site-Builder Dumps with Correct Answers
NEW QUESTION # 26
You have a website which is using a custom theme made specifically for that website. The client complains that content creators see an admin theme called "Claro" while creating or editing content. They want to see the content edit page in their own custom theme, but keep the other admin section in the Claro theme.
How can you achieve this?
- A. Give the Content Creator role permission to "View Admin Theme"
- B. On Appearance page, unselect the checkbox "See the administration theme when editing or creating content"
- C. Revoke the permission of viewing the custom theme for content creator role.
- D. On the Appearance page set admin theme as default theme
Answer: B
Explanation:
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 .
NEW QUESTION # 27
Your content team needs to use < div > tags in the content of some articles. The default configuration does not allow for this.
How can you reconfigure the site to support this request? (Select 2 options)
- A. Reconfigure the site's permissions; grant content editors the "Use advanced HTML" permission.
- B. Reconfigure the "Basic HTML" text format to allow the use of < div > tags.
- C. Enable the site theme's "structural HTML" setting.
- D. Reconfigure the page's body field to use the "Full HTML" text format.
Answer: B,D
Explanation:
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.
NEW QUESTION # 28
An audit of a corporate Drupal website revealed that a lot of user accounts are being created on the site, with the status "blocked". The site was initially set up to allow editors to self-register with additional administrator approval. However, the audit revealed that robots are creating a lot of user accounts and administrators are not able to keep up with the approval process.
How can we eliminate fake user registration?
- A. Configure new user accounts to "require email verification when a visitor creates an account."
- B. Enable the Drupal core captcha field on the user registration form.
- C. Hide user login by disabling the login block and/or move the login page.
- D. Change who can register accounts to "Administrators only."
Answer: B
Explanation:
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.
NEW QUESTION # 29
You have created a new View on the development environment.
How will you export the View to the production environment?
- A. This requires development effort and cannot be done by Drupal admin interface
- B. Use backup and migrate module to export the view
- C. Select synchronize configurations option on production environment
- D. Make the required changes to the development site. Partial export using single export option and import on the live site
Answer: D
Explanation:
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.
NEW QUESTION # 30
You run a site that attracts almost all of its users from France, even though you created the site in Australia. A number of users have started complaining that content publication times do not match their local time.
Which two solutions allow users to view content in their local timezone?
- A. Alter the default timezone to that of your target audience
- B. Set the default country to France
- C. Configure the content types to use France's timezone by default
- D. Check the "Users may set their own time zone" option in the Regional settings menu
Answer: A,D
Explanation:
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 .
NEW QUESTION # 31
You have created a new Comment type, but when you try to add a comment field to a Content type, you can't select your new Comment type.
- A. Custom comment types can only be added to default Content types.
- B. In your new Comment type, you didn't select "Content" as the Target entity type.
- C. You need to clear the site caches to see the new option.
- D. "Allow comments" is not checked in the Content type settings.
Answer: B
Explanation:
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.
NEW QUESTION # 32
What are the new features built into Drupal 10 core?
- A. User Groups, Taxonomy Access Control, Flags, Social Media Integration
- B. SEO Tools, Analytics, Social Sharing, Single Sign On (SSO)
- C. Webforms, Web Tokens, Page Rules, User Profiles
- D. Decoupled Menu, Starterkit for theme, Improved Layout Builder, CKEditor5
Answer: D
Explanation:
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.
NEW QUESTION # 33
You are using a contributed module named Lotus. You have read the module's documentation and ensured it is configured correctly. However, certain functionality of the module is not working as intended.
How should you find help?
(Select 2 options)
- A. Search for answers and ask questions in the module's issue queue on drupal.org.
- B. Ask questions in the drupal-support channel on IRC or in the support channel on Drupal Slack group.
- C. Create a comment of type "support request" on the module's project page.
- D. Email the module's maintainer and ask for help.
Answer: A,B
Explanation:
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.
NEW QUESTION # 34
You have a Corporate site where all traffic is anonymous. On the site, you have been getting thousands of user registrations every day. You notice that most of the registrations are spam.
What will you do to prevent this?
- A. Set the personal contact form for new users to disabled, and set email verification to use the personal contact form method.
- B. Add user/password in your .htaccess, so that only people who know the credentials can access your site and create an account.
- C. Set "Who can register accounts" to "Visitors," and check "Enable password strength indicator."
- D. Set "Who can register accounts" to "Administrators only," and assign the task of new account creation to site admins.
Answer: D
Explanation:
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.
NEW QUESTION # 35
A new customer has asked, why a Drupal-based website will be more flexible over a custom developed website.
Which THREE Drupal features would you explain to the customer?
- A. Drupal can be used as a headless CMS out of the box.
- B. Drupal provides comprehensive content modeling and listing of content using UI.
- C. Drupal has a comprehensive and feature rich administrative UI out of the box.
- D. Drupal.org has an online store where you can purchase modules and themes.
- E. Drupal allows you to directly rename database columns from the UI.
Answer: A,B,C
Explanation:
Drupal 10 and Drupal 11 are flexible because they provide major site-building capabilities through configuration and core modules, instead of requiring everything to be custom-coded. Drupal supports headless
/decoupled use cases out of the box through core web services such as JSON:API , which Drupal documentation describes as a standard way to expose site content for decoupled applications. That makes A correct.
Drupal also provides strong content modeling through entity types and fields, and it supports listing and displaying content through the Views UI . The User Guide and core documentation explain that site builders can define structured content types and then create listings, pages, blocks, sorting, and filtering through Views without writing custom code. That makes B correct.
Drupal additionally ships with a rich administrative interface for installing modules, managing themes, creating content types, editing fields, configuring permissions, and administering content. This is one of the platform's core strengths compared with a purely custom-built system, so E is correct.
Options C and D are not correct. Drupal.org provides contributed projects, but not an online store for buying modules and themes, and Drupal does not present direct database-column renaming as a normal UI-based site- building feature.
NEW QUESTION # 36
You have downloaded a contributed module and added it to modules/contrib folder on your Drupal site.
However, you are unable to install the module as the checkbox next to the module name appears disabled on the Extend page.
What could be the reason of this?
- A. You do not have 'install modules' permission
- B. A module on which the current module has a dependency is missing
- C. modules/contrib is incorrect folder for contributed modules
- D. The module was not downloaded using Drupal's UI
Answer: B
Explanation:
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.
NEW QUESTION # 37
You just installed Drupal 10 with a standard installation profile.
When you visit the User roles list, which three user roles are already available by default?
- A. Authenticated user
- B. Content editor
- C. Administrator
- D. Publisher
- E. Site builder
Answer: A,B,C
Explanation:
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 .
NEW QUESTION # 38
You have a content type "Places" which lists tourist destinations of different countries. You would like the visitors to be able to mark their country while commenting on "Places". This does not apply to other content types.
How will you build this functionality?
- A. Obtain country information from the user profile field while adding comments.
- B. Use the GeoIP module to tag users with their locations.
- C. Create a new comment type with a new field "Country" and associate it with Places content type.
- D. Create a "Country" vocabulary and add a term reference field to "Places" content type.
Answer: C
Explanation:
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.
NEW QUESTION # 39
You are building a recipe site in which users submit their favorite recipes as nodes, tagged with common ingredients from a carefully curated taxonomy vocabulary. You've been asked to create a page on which site visitors can select the ingredients they have on hand and view all the site's recipes that use those ingredients.
You've already created a view listing all Recipe nodes.
How can you modify the view to support filtering by ingredient?
- A. For each ingredient, create a separate view display with a contextual filter to limit results by that ingredient.
- B. Include a "Combine fields" filter that searches all fields for the ingredient name(s) the user enters.
- C. Add a menu block listing all ingredients. Each item in the menu block should link to a subdirectory URL associated with the listed ingredient.
- D. Create a filter using the Recipe content type's "Ingredients" field. Expose the filter to users, making sure it allows multiple selections.
Answer: D
Explanation:
Drupal's recommended way to let visitors narrow a Views listing by a field value is to add that field as a filter criterion and then expose the filter to site visitors . The core Views documentation explains that filters can be exposed so users can interact with the data shown in the view, instead of hard-coding separate displays or relying on free-text searching.
This question specifically says the recipes are tagged with a curated taxonomy vocabulary of ingredients.
Drupal's User Guide uses Ingredients as an example of a field that should be a taxonomy term reference , because the allowed values come from a managed list that can grow over time. That means the correct filter is the Recipe content type's Ingredients taxonomy-reference field in the View. Since visitors should be able to choose the ingredients they have on hand, the exposed filter should allow multiple selections .
The other options are not the standard Drupal site-building solution. Separate displays per ingredient do not scale, a combined-text search is not a structured taxonomy filter, and a menu block is navigation rather than a proper Views filter.
NEW QUESTION # 40
You have installed a custom theme for your website, and you notice that the theme displays a Drupal icon as the favicon in the browser. As much as you love Drupal, you would like to remove this favicon and display your company's favicon instead.
How would you do this in the Drupal admin interface?
- A. Place the Site branding block in the appropriate region and enable the favicon under "Toggle branding elements".
- B. Go to Appearance > Settings and upload your new favicon.
- C. Go to Configuration > Basic Site Settings and upload your new favicon.
- D. Use a contributed module to inject CSS to hide the Druplicon and display your logo instead.
Answer: B
Explanation:
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.
NEW QUESTION # 41
You have created a new Article node with a title, an image and a body field. Your site is configured to use Drupal's core search. If you search for a phrase which is used in your new article, the article is not returned in the search results. Search is otherwise working correctly.
Why is your article not appearing in the search results?
- A. The core search module must be configured to recognize the search term.
- B. Drupal core search does not work very well, and you should use a contributed module for search instead.
- C. Cron has not run since you added the article, so Drupal has not indexed the new article yet.
- D. You did not check the "Add to search index" checkbox when creating your article.
Answer: C
Explanation:
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.
NEW QUESTION # 42
You manage a local restaurants guide website. You are creating a page listing all the restaurants registered on your site. You've been asked to make sure that each restaurant in the list includes an image, a title, and cuisine style. When the user clicks the title or picture, the user will be taken to a detail page showing a full description of the restaurant.
Which 2 options will ensure that the listing page only contains the fields noted, without removing the description field from the detail page?
- A. Use the Views module to create a list of all restaurants, and make sure it displays each restaurant row as fields. Add the image, title, and cuisine fields to the view's field list.
- B. Use the Views module to create a list of all restaurants. Configure the view to hide the description field by adding a custom CSS class to its wrapper.
- C. Create a second content type called "Restaurant Overview," which only contains the image, title, and cuisine fields. Use the Views module to create a list of all of these Restaurant Overview nodes, but link their titles to their corresponding Restaurant nodes.
- D. Use custom display settings for the "Teaser" view mode and configure it to display only the image, title, and cuisine fields. Use the Views module to create a list of all restaurants, displaying each row as content using the "Teaser" view mode.
Answer: A,D
Explanation:
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.
NEW QUESTION # 43
The UX team has suggested that "Social share" buttons currently visible in the sidebar region should be moved to the footer. The Social share buttons are implemented in a custom block.
How should you make the requested changes?
- A. From the "Appearance" admin page, reconfigure the site's theme to place the block in the Footer region instead of the Sidebar.
- B. Using the "Basic page" content type's "Manage display" interface, drag the existing block from the Sidebar region to the Footer region.
- C. For each content type, use the Layout Builder module's "manage layout" feature to reassign the block from the Sidebar region to the Footer region.
- D. From the block layout admin page, drag the existing block from the Sidebar region to the Footer region.
Answer: D
Explanation:
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.
NEW QUESTION # 44
You are building a bi-lingual site which is in English and Spanish. You have created all the English content.
How will you add Spanish translation to existing content?
- A. On the Translate tab of each node, add Spanish translations manually.
- B. On the Content overview page, select all English content. Check "Import Translations" from the Bulk Actions dropdown.
- C. Download the Spanish .po files from localize.drupal.org. Import the .po file.
- D. On Admin > Translate page, enable the Add Google Translations checkbox to import all Spanish translations.
Answer: A
Explanation:
In Drupal 10 and Drupal 11, content translation is handled through the Content Translation module , which allows you to translate individual content entities (such as nodes). Once multilingual support is enabled and a new language (Spanish) is added, each piece of content provides a Translate tab where translations can be created and managed.
Drupal's User Guide explains that to translate existing content, you navigate to the content item and use the Translate tab to add a translation in the desired language. This process allows editors to manually enter translated content for each field, ensuring accuracy and proper localization.
Option B is incorrect because Drupal core does not provide automatic Google translation import functionality.
Option C refers to interface translation (.po files), which is used for translating the Drupal UI, not site content.
Option D is incorrect because Drupal does not provide a bulk "Import Translations" action for node content in this manner.
Therefore, the correct and documented approach is to manually add translations via the Translate tab for each content item, making A the correct answer.
NEW QUESTION # 45
The development team does monthly releases to the production system. The deployment lasts for an hour.
During the deployment time, the site is put into maintenance mode. You want a certain set of users to be able to access the site during maintenance mode as well.
How do you accomplish this?
- A. Under permissions page, provide permission "Administer site" to required users
- B. Only administrators can access the site during maintenance mode
- C. Create a new role, assign users to the role and provide permission "Use the site in maintenance mode" to new role
- D. Create a new role, assign users to the role. Go to Configuration # Development # Maintenance mode and select role to allow access
Answer: C
Explanation:
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.
NEW QUESTION # 46
Your site has three Content types with a Media reference field. The field is configured to Media type as Image. You noticed that some users are adding animated GIF files while adding the content, which are very distracting.
How can you disallow adding files with .gif extension on all the Content types which use the Media reference field?
- A. Edit the Content types and disallow .gif extension in the Media reference field settings.
- B. Edit the Content types and update Media field settings in Manage form display tab.
- C. Edit the Media type Image and update media type settings to disallow .gif files.
- D. Edit the Media type Image and remove gif from "image" field settings in the Manage fields tab.
Answer: D
NEW QUESTION # 47
......
Dumps of Drupal-Site-Builder Cover all the requirements of the Real Exam: https://www.troytecdumps.com/Drupal-Site-Builder-troytec-exam-dumps.html