BlackFriday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Acquia Exam Acquia-Certified-Site-Builder-D8 Topic 1 Question 74 Discussion

Actual exam question for Acquia's Acquia-Certified-Site-Builder-D8 exam
Question #: 74
Topic #: 1
[All Acquia-Certified-Site-Builder-D8 Questions]

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?

Show Suggested Answer Hide Answer
Suggested Answer: B

by Alethea at Sep 08, 2024, 01:46 AM

Limited Time Offer

25%

Off

Get Premium Acquia-Certified-Site-Builder-D8 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Colton
1 months ago
Ah, the old 'copy the database' trick. Classic move, but I'd rather not risk it. Configuration export FTW!
upvoted 0 times
Dean
2 days ago
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.
upvoted 0 times
...
Elenora
7 days ago
A) 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.
upvoted 0 times
...
...
Nettie
1 months ago
I think we should stick with option A to ensure a smoother transition to production.
upvoted 0 times
...
Glynda
1 months ago
That's true, but it might be risky to directly copy the production database into staging.
upvoted 0 times
...
Erick
1 months ago
Option D looks tempting, but copying databases can introduce all sorts of issues. Better to stick with configuration management.
upvoted 0 times
...
Louvenia
2 months ago
Option C is a trap! Sharing the database between staging and production is a recipe for disaster. That's a big no-no.
upvoted 0 times
Erasmo
18 days ago
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.
upvoted 0 times
...
Amalia
28 days ago
Option C is a trap! Sharing the database between staging and production is a recipe for disaster. That's a big no-no.
upvoted 0 times
...
Marsha
1 months ago
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.
upvoted 0 times
...
Leslie
1 months ago
A) 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.
upvoted 0 times
...
...
Kattie
2 months ago
But wouldn't option D be faster since you're copying the production database?
upvoted 0 times
...
Nettie
2 months ago
I agree with Glynda, exporting the site configuration to code seems like the best way to go.
upvoted 0 times
...
Holley
2 months ago
I'd go with Option B. Leveraging the existing codebase and just importing the site configuration is more efficient than a full copy of the site.
upvoted 0 times
Adelle
1 months ago
A) 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.
upvoted 0 times
...
Wilbert
1 months ago
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.
upvoted 0 times
...
Vilma
1 months ago
A) 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.
upvoted 0 times
...
...
Dexter
2 months ago
Option A seems the safest approach. Exporting the configuration to code and then importing it to different environments ensures consistency and control.
upvoted 0 times
Justa
2 months ago
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.
upvoted 0 times
...
Eloisa
2 months ago
A) 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.
upvoted 0 times
...
...
Glynda
2 months ago
I think option A sounds like a good approach.
upvoted 0 times
...

Save Cancel