New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Adobe AD0-E706 Exam - Topic 12 Question 36 Discussion

Actual exam question for Adobe's AD0-E706 exam
Question #: 36
Topic #: 12
[All AD0-E706 Questions]

You are setting up a third-party integration only for the Production environment, which connects to an external RabbitMQ server.

Where do you put the configuration?

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

0/2000 characters
Joana
3 months ago
I had no idea it could go in the magento env yaml file!
upvoted 0 times
...
Galen
3 months ago
I agree, QUEUE_CONFIGURATION seems more secure!
upvoted 0 times
...
Claudio
3 months ago
Wait, isn't that risky for production?
upvoted 0 times
...
Whitney
4 months ago
I think env.php is the right place, though.
upvoted 0 times
...
Myong
4 months ago
Definitely in the QUEUE_CONFIGURATION variable!
upvoted 0 times
...
Lisandra
4 months ago
I’m a bit confused; I thought we were supposed to use the magento-cloud CLI for this kind of setup, but I can’t recall the exact details.
upvoted 0 times
...
Lili
4 months ago
I feel like the QUEUE_CONFIGURATION variable in the magento env yaml file is the right choice, but I might be mixing it up with another topic we covered.
upvoted 0 times
...
Patria
4 months ago
I remember practicing a similar question, and I think the env.php file is more for general settings, not specific integrations like RabbitMQ.
upvoted 0 times
...
Lourdes
5 months ago
I think the configuration should go in the QUEUE_CONFIGURATION variable, but I'm not entirely sure if it's the one in the Web UI or the YAML file.
upvoted 0 times
...
Reed
5 months ago
Okay, let me think this through. Since this is a third-party integration, I'm guessing the configuration should be stored in an environment variable, rather than in a static config file. I'll go with option B.
upvoted 0 times
...
Jacquline
5 months ago
Hmm, I'm not sure about this one. I know we need to set up the RabbitMQ integration for the Production environment, but I'm not familiar with the different configuration files. I'll have to review the documentation carefully.
upvoted 0 times
...
Nenita
5 months ago
This looks straightforward. I think the configuration should go in the magento-cloud.yaml file, since that's where we typically store environment-specific settings.
upvoted 0 times
...
Alida
5 months ago
I'm confident this is an environment-specific setting, so it should be in the magento-cloud.yaml file. That's where we typically put configuration that needs to be different across environments.
upvoted 0 times
...
Jacquelyne
5 months ago
Okay, I know RAID1 is mirroring, RAID5 is striping with parity, and RAID0 is striping without parity. I think RAID6 might be the best option here, but I'll double-check the SAP requirements to be sure.
upvoted 0 times
...
Jani
5 months ago
Hmm, this seems like a tricky one. I'll need to think through the steps carefully to make sure I don't miss anything.
upvoted 0 times
...
Carey
9 months ago
Option B is the way to go. Who wants to dig through a messy env.php file when you can just update the QUEUE_CONFIGURATION settings in the UI or CLI? Easy peasy.
upvoted 0 times
...
Dustin
10 months ago
Ha! Putting the config in the QUEUE_CONFIGURATION variable? Sounds like a real queue configuration to me!
upvoted 0 times
...
Amina
10 months ago
I think B is the right choice here. Keeping the configuration separate from the app/etc/env.php file makes it easier to manage and update the settings for the Production environment.
upvoted 0 times
Alpha
8 months ago
C) In the QUEUE_CONFIGURATION variable in the magento env yaml file
upvoted 0 times
...
Linwood
9 months ago
I agree, it's better to keep the configuration separate for easier management.
upvoted 0 times
...
Shonda
9 months ago
B) In the QUEUE_CONFIGURATION variable added in the project Web UI or magento-cloud CLI
upvoted 0 times
...
...
Buddy
10 months ago
The correct answer is B. Definitely putting the configuration in the QUEUE_CONFIGURATION variable added in the project Web UI or Magento-cloud CLI makes the most sense for a third-party integration in the Production environment.
upvoted 0 times
Glen
10 months ago
B) In the QUEUE_CONFIGURATION variable added in the project Web UI or Magento-cloud CLI
upvoted 0 times
...
Jamie
10 months ago
A) In the app/etc/env.php file
upvoted 0 times
...
...
Edelmira
10 months ago
I personally prefer putting it in the QUEUE_CONFIGURATION variable in the magento env.yaml file for better organization.
upvoted 0 times
...
Leila
11 months ago
I disagree, I believe it should be in the QUEUE_CONFIGURATION variable added in the project Web UI or magento-cloud CLI.
upvoted 0 times
...
Irving
11 months ago
I think the configuration should go in the app/etc/env.php file.
upvoted 0 times
...

Save Cancel