Acquia Drupal-Site-Builder認證考試是目前IT人士報名參加的考試中很受歡迎的一個認證考試。通過了Acquia Drupal-Site-Builder認證考試不僅能使你工作和生活帶來提升，而且還能鞏固你在IT 領域的地位。但是事實情況是它通過率確很低。
| Section | Objectives |
|---|---|
| Topic 1: Theming and Layout Basics | - Frontend structure
|
| Topic 2: Site Building with Views | - Views configuration
|
| Topic 3: Content Management and Display | - Content display configuration
|
| Topic 4: Drupal Site Building Fundamentals | - Content architecture concepts
|
| Topic 5: Security, Performance, and Best Practices | - Site maintenance
|
| Topic 6: Configuration and Site Setup | - Site configuration basics
|
| Topic 7: User Management and Permissions | - User administration
|
Fast2test是個為Acquia Drupal-Site-Builder 認證考試提供短期的有效培訓的網站，但是Fast2test能保證你的Acquia Drupal-Site-Builder 認證考試及格。如果你不及格，我們會全額退款。在你選擇購買Fast2test的產品之前，你可以在Fast2test的網站上免費下載我們提供的部分關於Acquia Drupal-Site-Builder認證考試的練習題及答案作為嘗試，那樣你會更有信心選擇Fast2test的產品來準備你的Acquia Drupal-Site-Builder 認證考試。
問題 #46
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?
答案：B
解題說明：
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 .
問題 #47
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?
答案：D
解題說明：
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.
問題 #48
Your website has a content type named "Cars for sale" with a Taxonomy reference field for "Manufacturer" vocabulary. You have a view listing all the cars for sale. You wish to display different background colors to the cars rows based on the value of the Manufacturer field.
How can you add a CSS class to each row of the view based on the value of the Manufacturer field?
答案：B
解題說明：
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 .
問題 #49
What are the new features built into Drupal 10 core?
答案：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.
問題 #50
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?
答案：B
解題說明：
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.
問題 #51
......
在Fast2test的網站上你可以免費下載Fast2test為你提供的關於Acquia Drupal-Site-Builder 認證考試學習指南和部分練習題及答案作為嘗試。
新版Drupal-Site-Builder題庫: https://tw.fast2test.com/Drupal-Site-Builder-premium-file.html