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?

• A. Configuration created in the staging environment is automatically available to the production environment since they share a database.
• B. Copy the production database into the staging environment. Create the fields and View there. Once QA is satisfied, copy the staging database into the production environment.
• C. Create the fields and View in a fresh installation of Drupal core. Export the site configuration into your site's existing codebase, push the code to the staging environment, and import the site configuration there. Once QA is satisfied, repeat the process in production.
• D. Create the fields and View in a development copy of the site. Export the site configuration to code.Push that code to the staging environment and import the site configuration there. Once QA is satisfied, repeat the process in production.

You are building a gaming site where users are teamed based on their favorite weapon.
How will you provide the ability for users to select their favorite weapon?

• A. Create a vocabulary with a list of weapons as terms and check the "Display on user profile" checkbox.
• B. Create a Content Type "Users" which has "Favorite Weapon" field. Use the content type as user profiles.
• C. Create a Content Type "Weapons" and create a view. Show this view on /user.
• D. In Account settings, go to Manage fields and add field for "Favorite weapon"

What is meant by headless Drupal?
(Select 2 options)

• A. Just another phrase for "decoupled Drupal"
• B. Exposing Drupal content to other systems such as native applications.
• C. Publishing content automatically in Drupal
• D. Applying security updates automatically to Drupal installation

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 Media type Image and update media type settings to disallow .gif files.
• B. Edit the Content types and update Media field settings in Manage form display tab.
• C. Edit the Content types and disallow .gif extension in the Media reference field settings.
• D. Edit the Media type Image and remove gif from "image" field settings in the Manage fields tab.

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. On the Appearance page set admin theme as default theme
• D. Revoke the permission of viewing the custom theme for content creator role.