我々のDrupal-Site-Builder試験に何か疑問があったら、我々の係員をオンラインで連絡してください。ほかの人の話しより自分で体験したほうがいいと言われています。我々のサイトで無料なDrupal-Site-Builder問題集のサンプルが提供されています。あなたは我々の言うことが依然として信じられないなら、我々のサンプルを無料でダウンロードしてみることができます。
| Section | Weight | Objectives |
|---|---|---|
| Topic 1: Site Building Fundamentals | 20% | - Taxonomy Architecture - Entity Reference Relationships - Content Workflow and States - Content Types and Fields |
| Topic 2: Site Configuration | 15% | - Search Configuration - Module Configuration - Configuration Management - User Role and Permission Management |
| Topic 3: Multilingual and Internationalization | 10% | - Language Configuration - Content Translation - Interface Translation - Configuration Translation |
| Topic 4: Layout and User Interface | 20% | - View Modes and Display Settings - Layout Builder - Block System and Placement - Theme Configuration |
| Topic 5: Drupal 10/11 Specific Features | 15% | - JSON:API and REST Configuration - Modern Module Usage - Olivero and Claro Themes - CKEditor 5 Configuration |
| Topic 6: Site Display and Presentation | 20% | - Webform Integration - Views Displays and Filters - Views Module Fundamentals - Media Management |
>> Drupal-Site-Builderウェブトレーニング <<
たくさんの人はAcquia Drupal-Site-Builder「Acquia Certified Drupal Site Builder Exam for Drupal 10, 11」認証試験を通ることが難しいと思います。もし弊社の問題集を勉強してそれは簡単になります。弊社はオンラインサービスとアフターサービスとオンラインなどの全面方面を含めてます。オンラインサービスは研究資料模擬练習問題などで、アフターサービスはTech4Examが最新の認定問題だけでなく、絶えずに問題集を更新しています。
質問 # 41
While building a new site, you are working with the default frontend theme. You have placed custom blocks in available regions. After some time, you decide to install a new contributed theme, and set it as the default for the site.
After switching to the new theme, you notice that many of your blocks have disappeared!
What is the likely reason for this?
正解：A
解説：
In Drupal 10 and Drupal 11, block placement is defined per theme . The Block Layout documentation explains that when placing a block, you are assigning it to a region in a specific theme , not globally for all themes. So when you switch the site's default theme, the new theme may have a different set of regions or different region names, and block placements from the previous theme may no longer map correctly.
Drupal's theming documentation is even more explicit: if a theme does not define a region that blocks were assigned to, those blocks are treated as assigned to an invalid region and are disabled . The Block module documentation also states that disabled blocks (blocks not assigned to any region in your theme) are never shown . This is exactly why blocks can appear to "disappear" after changing themes.
The other options do not match Drupal's documented behavior. Blocks do not need to be "registered" with a theme in this sense, contributed themes are not limited to system blocks, and custom blocks generally do not need to be recreated just because the theme changed. The issue is the theme-specific region mapping , which makes D the correct answer.
質問 # 42
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)
正解：B、C
解説：
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.
質問 # 43
Your client wishes to retain past versions of the site content by default.
How do you accomplish this?
正解：B
解説：
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.
質問 # 44
You have enabled website feedback contact form to allow users to submit feedback. You would like to redirect users to a different page after submission.
How will you accomplish this?
正解：A
解説：
Drupal core's Contact module allows administrators to configure multiple contact forms, each with its own settings. One of the configurable options is the ability to define a redirect path after form submission. This is done within the specific contact form's configuration, where you can specify the destination page users should be taken to after submitting the form.
Option D is correct because Drupal provides a "Redirect path" setting directly in the contact form configuration , making it possible to send users to a custom page such as a thank-you or confirmation page after submission.
Option A is incorrect because Drupal core already supports this functionality without needing a contributed module like Webform. Option B is incorrect because Site information settings do not control form submission redirects. Option C is not relevant, as redirect behavior is not controlled through user profiles.
Thus, the correct Drupal-native solution is to configure the redirect path within the contact form settings, making D the correct answer.
質問 # 45
Your client copies HTML from an external source and pastes into the default WYSIWYG Editor on your site (CKEditor). The client has come to you complaining of broken HTML being displayed on the site. The CKEditor is configured to use Full HTML text format allowing all HTML elements and should continue to allow all elements.
How would you fix the issue of broken HTML?
正解：D
解説：
Drupal uses text formats and filters to control how HTML input is processed before being displayed. One of the available filters is "Correct faulty and chopped off HTML" , which is specifically designed to fix improperly formatted or broken HTML markup.
According to Drupal documentation, this filter ensures that HTML pasted into editors (like CKEditor) is automatically cleaned and corrected , such as closing unclosed tags, fixing malformed markup, and preventing rendering issues. This is particularly useful when users paste HTML from external sources, which often includes inconsistent or invalid markup.
Option D is correct because it directly addresses the issue at the text format level without restricting allowed tags, maintaining the requirement to allow all HTML elements.
Option C is incorrect because enabling "Limit allowed HTML tags" would restrict HTML usage, which contradicts the requirement to allow all elements. Options A and B are not standard Drupal solutions and do not align with Drupal's built-in filtering system.
Therefore, enabling the Correct faulty and chopped off HTML filter is the correct and recommended approach in Drupal 10 and Drupal 11.
質問 # 46
......
時間が経つとともに、我々はインタネット時代に生活します。この時代にはIT資格認証を取得するは重要になります。それでは、Drupal-Site-Builder試験に参加しよう人々は弊社Tech4ExamのDrupal-Site-Builder問題集を選らんで勉強して、一発合格して、AcquiaIT資格証明書を受け取れます。
Drupal-Site-Builder問題集無料: https://www.tech4exam.com/Drupal-Site-Builder-pass-shiken.html