Deal of The Day! 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 4 Question 82 Discussion

Actual exam question for Acquia's Acquia-Certified-Site-Builder-D8 exam
Question #: 82
Topic #: 4
[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 Frankie at Dec 08, 2024, 10:57 PM

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
Gianna
13 days ago
A is the clear winner. Export, push, import - it's the classic Drupal site build workflow. Can't go wrong with that.
upvoted 0 times
...
Gerald
14 days ago
I bet the person who wrote option C also believes in the tooth fairy. Definitely not the right answer here.
upvoted 0 times
...
Vivan
21 days ago
But with option B, we might run into compatibility issues with our existing codebase. Option A provides a more controlled process.
upvoted 0 times
...
Barrett
29 days ago
I prefer option B. It seems more straightforward to me to start with a fresh installation of Drupal core.
upvoted 0 times
...
Hollis
1 months ago
D? Really? Copying the production database to staging? That's a disaster waiting to happen. A all the way.
upvoted 0 times
...
Glynda
1 months ago
C is just wrong. Configuration changes don't magically sync across environments just because they share a database. That's not how it works.
upvoted 0 times
Ellsworth
11 days ago
A
upvoted 0 times
...
...
Amos
1 months ago
Hmm, I'm not sure about B. Exporting the config into the existing codebase could be risky if there are any conflicts. A seems cleaner to me.
upvoted 0 times
Berry
22 days ago
Yeah, I think exporting the site configuration to code in a development copy is the way to go.
upvoted 0 times
...
Miesha
28 days ago
I agree, B does sound risky. A seems like a safer option.
upvoted 0 times
...
...
Jennifer
1 months ago
I agree with Vivan. Option A ensures that we can make changes without affecting the live site.
upvoted 0 times
...
Vivan
1 months ago
I think option A is the best approach. It allows us to develop and test in a separate environment before pushing to production.
upvoted 0 times
...
Lamonica
1 months ago
Option A seems like the way to go here. Exporting the configuration to code and pushing it to staging for QA review is the safest approach.
upvoted 0 times
Rosamond
7 days ago
Definitely, it's better to be safe than sorry when it comes to making changes to a busy site like this.
upvoted 0 times
...
Audry
9 days ago
That way we can catch any issues before they impact the live site and its comment activity.
upvoted 0 times
...
Skye
18 days ago
I agree, it's important to test everything in staging before making changes to the production site.
upvoted 0 times
...
Lasandra
29 days ago
Option A seems like the way to go here. Exporting the configuration to code and pushing it to staging for QA review is the safest approach.
upvoted 0 times
...
...

Save Cancel