You’ve been asked to add several new fields and a view for the news area of a site with a very busy comments section The QA team wants to review your work in staging before rolling everything out to production all at once.
How can you meet these requirements without interfering with the production site’s comment activity or 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. 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.
- C. 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.
- D. 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.