学歴は実力と等しくなく、能力とも等しくないです。本当の能力は実践で鍛えたもので、学歴と直接な関係がないです。「私はだめです。」と思わないでください。AcquiaのDrupal-Site-Builder試験に申し込んだあなたは自分が合格できないなんてを心配だったら、JapancertのAcquiaのDrupal-Site-Builder試験トレーニング資料を利用してください。学歴がどんなに高くて、能力がどんなに低くても、首尾よく試験に合格することができます。
| Section | Weight | Objectives |
|---|---|---|
| Contributed Module and Theme Management | 12% | - Add, update, remove contributed modules - Community participation and issue reporting - Add, update, remove contributed themes |
| Content Modeling | 28% | - Block types and blocks configuration - Content types and vocabularies - Rich media usage via Media module - Comment types and comments management - Multilingual content and interface configuration - Menus, menu items and menu blocks - Contact forms setup and management |
| Understanding Drupal and working with a Drupal Site | 12% | - Troubleshooting content, configuration and maintenance issues - Content vs block differentiation - Drupal features and terminology |
| Site Display | 20% | - Content display control using block system - Layout building with Layout Builder - Content lists creation and management with Views - Entity presentation customization |
| Security and Performance | 8% | - Security risks from configuration - Performance impacts from configuration |
| Site Configuration | 20% | - User accounts and permissions setup - Configuration import, export, synchronization - Core site settings: accounts, content, search, media etc. |
AcquiaのDrupal-Site-Builder試験の合格書は君の仕事の上で更に一歩の昇進と生活条件の向上を助けられて、大きな財産に相当します。AcquiaのDrupal-Site-Builder認定試験はIT専門知識のレベルの考察として、とっても重要な地位になりつつます。Japancertは最も正確なAcquiaのDrupal-Site-Builder試験資料を追求しています。
質問 # 33
You manage a popular news portal which has a very busy comments section. You've been asked to add several new fields and a View for the news area of a site. The QA team wants to review your work in staging before rolling everything out to production at once. The editorial team has specified that the site's comments activity should not be affected by these changes.
How can you meet these requirements without having to create the new functionality independently in both environments?
正解：C
解説：
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.
質問 # 34
Your Marketing Department notified you that the company has recently obtained a new Toll-free phone number for customer care. They have asked you to update the "Customer care contact information" posted on your website with the new number. The contact information appears in the sidebar of every page on the site.
How should you make your updates? (Select 2 options)
正解：C、D
解説：
In Drupal 10 and Drupal 11, content that appears in the sidebar across all pages is typically implemented as a custom block placed in a theme region via the Block Layout system. Drupal documentation explains that reusable content like contact information is best managed through custom blocks , which can be edited centrally and automatically update everywhere they are placed.
Option A is correct because the proper way to update such content is to go to Structure # Block layout # Custom block library , locate the block, and edit it. This ensures the change is reflected globally wherever the block is used.
Option C is also correct because Drupal provides contextual links (the pencil icon) that allow administrators to directly edit blocks from the front end. This is a standard and documented shortcut for editing block content.
Option B is incorrect because Layout Builder is not mentioned and is not required here. Option D is incorrect because editing individual pages would not update a shared sidebar block and would be inefficient and incorrect.
Thus, the correct Drupal site-building approaches are editing the custom block via the block library or using contextual links, making A and C correct.
質問 # 35
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?
正解：B
解説：
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.
質問 # 36
Users are complaining that listing pages with a large number of images are loading very slowly. On reviewing this you found that full-sized images are loaded while displaying thumbnails.
How will you ensure that smaller sized images are used as thumbnails?
正解：A
解説：
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.
質問 # 37
You installed a new site using the Spanish language. You added new fields to article content type alongside the default fields. The custom fields labels are in Spanish.
Which of the following statements is true when you add the French language to your site?
正解：D
解説：
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.
質問 # 38
......
私たち全員が知っているように、試験の準備プロセスは非常に面倒で時間がかかります。 Drupal-Site-Builder試験の準備のために他のことをするために時間を割く必要があり、多くの重要なことが遅れました。この問題に直面した場合は、Drupal-Site-Builderの実際の試験を選択してください。教材を使用すると、試験に参加できるのは準備に約20〜30時間かかる場合のみです。残りの時間は、やりたいことを何でもできます。これにより、レビューのプレッシャーを完全に軽減できます。
Drupal-Site-Builder試験勉強過去問: https://www.japancert.com/Drupal-Site-Builder.html