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

Adobe Exam AD0-E706 Topic 11 Question 25 Discussion

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

For the Magento search backend you would like lo move from MySQL lo Elasticsearch for your existing project. You have confirmed that your services. yaml file is configured appropriately However, after your most recently deployment, you notice the search engine is still set to MySQL

What additional step must be completed?

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

Erasmo
11 days ago
I'm leaning towards C too. Magento loves to hide important settings in the admin panel, doesn't it? Gotta love these enterprise-level surprises.
upvoted 0 times
...
Alverta
12 days ago
Haha, you'd think just configuring the services.yaml file would be enough, but nope, Magento always has to make things a little more complicated. I'm going with C as well.
upvoted 0 times
...
Mammie
17 days ago
I'm not sure, but I think we also need to find an appropriate Elasticsearch module to require with Composer. So, maybe the answer is a combination of B) and C).
upvoted 0 times
...
Claribel
18 days ago
I think the answer is C. It's not enough to just configure the services.yaml file - you also need to specify Elasticsearch as the search engine in the Magento Admin panel.
upvoted 0 times
...
Ciara
21 days ago
I agree with Francine. Configuring Elasticsearch in the Magento Admin panel should solve the issue.
upvoted 0 times
...
Francine
21 days ago
I think the correct answer is C) Specify Elasticsearch as the search engine in the Magento Admin panel.
upvoted 0 times
...
Emogene
24 days ago
I'm not sure, but I think we also need to find an appropriate Elasticsearch module to require with Composer. So, maybe the answer is a combination of B) and C).
upvoted 0 times
...
Carmela
24 days ago
I agree with Paz. Configuring Elasticsearch in the Magento Admin panel should solve the issue.
upvoted 0 times
...
Paz
28 days ago
I think the correct answer is C) Specify Elasticsearch as the search engine in the Magento Admin panel.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77