あなたはいまAcquiaのDrupal-Site-Builder認定試験にどうやって合格できるかということで首を傾けているのですか。AcquiaのDrupal-Site-Builder認定試験は現在のいろいろなIT認定試験における最も価値のある資格の一つです。ここ数十年間では、インターネット・テクノロジーは世界中の人々の注目を集めているのです。それがもう現代生活の不可欠な一部となりました。その中で、Acquiaの認証資格は広範な国際的な認可を得ました。ですから、IT業界で仕事している皆さんはAcquiaの認定試験を受験して資格を取得することを通して、彼らの知識やスキルを向上させます。Drupal-Site-Builder認定試験はAcquiaの最も重要な試験の一つです。この資格は皆さんに大きな利益をもたらすことができます。
| Section | Weight | Objectives |
|---|---|---|
| Content Modeling | 28% | - Rich media usage via Media module - Contact forms setup and management - Block types and blocks configuration - Menus, menu items and menu blocks - Comment types and comments management - Multilingual content and interface configuration - Content types and vocabularies |
| Site Display | 20% | - Content display control using block system - Entity presentation customization - Layout building with Layout Builder - Content lists creation and management with Views |
| Contributed Module and Theme Management | 12% | - Community participation and issue reporting - Add, update, remove contributed themes - Add, update, remove contributed modules |
| Security and Performance | 8% | - Security risks from configuration - Performance impacts from configuration |
| Site Configuration | 20% | - Core site settings: accounts, content, search, media etc. - Configuration import, export, synchronization - User accounts and permissions setup |
| Understanding Drupal and working with a Drupal Site | 12% | - Content vs block differentiation - Troubleshooting content, configuration and maintenance issues - Drupal features and terminology |
今の競争の激しいIT業界ではAcquiaのDrupal-Site-Builder試験にパスした方はメリットがおおくなります。給料もほかの人と比べて高くて仕事の内容も豊富です。でも、この試験はそれほど簡単ではありません。
質問 # 26
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
解説：
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.
質問 # 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、B
質問 # 28
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?
正解：C
解説：
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.
質問 # 29
The site you are managing has a "Comments approval" process. You have moderators with appropriate permissions to review and approve comments. The moderators want to see all the unapproved comments sorted by the node on which they are posted, but they can't do this on the Comments approval page.
What is the simplest way to solve this problem?
正解：B
解説：
In Drupal 10 and Drupal 11, the administrative Comments listing is provided by the core comment View. In core's default views.view.comment configuration, the comments administration display uses the table style, includes the entity_id field labeled "Posted in" , and that column is present in the table configuration.
However, core sets that column's table option to sortable: false , while other columns such as Subject, Author, and Updated are sortable. That is why moderators cannot sort the approval page by the content item the comment belongs to, even though the field is already there.
Because the existing approval page already uses a View, the simplest solution is to edit that View and enable sorting for the Entity ID / Posted in column in the table settings. Creating a brand-new View would work, but it is not the simplest option because it duplicates an existing administrative display. The other options do not address the actual issue with the current moderation screen. Drupal's content administration documentation also confirms that comments are managed from the Comments administration page, making improvement of that interface the most appropriate site-building solution.
質問 # 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?
正解：B、D
解説：
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 .
質問 # 31
......
試験を受けることでAcquia認定を取得することを期待する人が増えています。ただし、多くの人にとって試験は非常に困難です。特に正しい学習教材を選択せずに適切な方法を見つけた場合、Drupal-Site-Builder試験に合格して関連する認定を取得することはより困難になります。関連する認定を効率的な方法で取得したい場合は、当社のDrupal-Site-Builder学習教材を選択してください。弊社のDrupal-Site-Builder学習教材が試験に合格し、簡単に認定を取得するのに役立ちます。
Drupal-Site-Builderシュミレーション問題集: https://www.mogiexam.com/Drupal-Site-Builder-exam.html