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 have created a new Comment type, but when you try to add a comment field to a Content type, you can't select your new Comment type.

What could be the problem'?

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
3 months 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
3 months ago
I bet the person who wrote option C also believes in the tooth fairy. Definitely not the right answer here.
upvoted 0 times
Pearly
2 months ago
Yeah, option C doesn't seem like the best approach. It's important to keep production and staging separate to avoid any issues.
upvoted 0 times
...
Stacey
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
...
Justine
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
...
...
Vivan
3 months 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
4 months ago
I prefer option B. It seems more straightforward to me to start with a fresh installation of Drupal core.
upvoted 0 times
...
Hollis
4 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
4 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
Jarod
2 months ago
D
upvoted 0 times
...
Tori
3 months ago
B
upvoted 0 times
...
Ellsworth
3 months ago
A
upvoted 0 times
...
...
Amos
4 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
4 months ago
Yeah, I think exporting the site configuration to code in a development copy is the way to go.
upvoted 0 times
...
Miesha
4 months ago
I agree, B does sound risky. A seems like a safer option.
upvoted 0 times
...
...
Jennifer
4 months ago
I agree with Vivan. Option A ensures that we can make changes without affecting the live site.
upvoted 0 times
...
Vivan
4 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
4 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
3 months 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
3 months ago
That way we can catch any issues before they impact the live site and its comment activity.
upvoted 0 times
...
Skye
3 months ago
I agree, it's important to test everything in staging before making changes to the production site.
upvoted 0 times
...
Lasandra
4 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
...
...

Save Cancel