Adobe Exam AD0-E706 Topic 11 Question 25 Discussion

Actual exam question for Adobe's AD0-E706 exam

Question #: 25
Topic #: 11

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?

AConfigure the relationships Section of the .magento.app.yaml file

BFind an appropriate Elasticsearch module to require with Composer

CSpecify Elasticsearch as the search engine in the Magento Admin panel

DRemove the MySQL service from the services. yaml file

Show Suggested Answer

Suggested Answer: C

by Charlene at Jan 28, 2024, 11:53 PM

Limited Time Offer

25%

Off

Get Premium AD0-E706 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Wenona

1 months ago

I'm feeling a bit like a magician trying to keep up with all these Magento tricks. But C seems like the obvious choice here. Time to go configure that admin panel!

upvoted 0 times

Jennifer

4 days ago

That's right! The admin panel is where you can make that change.

upvoted 0 times

...

Tonette

9 days ago

C) Specify Elasticsearch as the search engine in the Magento Admin panel

upvoted 0 times

...

Erasmo

2 months 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

Cherry

1 days ago

Definitely. It's like a treasure hunt with these enterprise-level surprises.

upvoted 0 times

...

Leonor

2 days ago

I've had similar experiences with Magento. It's all about digging through the admin panel.

upvoted 0 times

...

Justa

14 days ago

Yeah, I agree. It's always a challenge to find the right settings.

upvoted 0 times

...

Ollie

28 days ago

I think C is the right choice. Magento can be tricky sometimes.

upvoted 0 times

...

Alverta

2 months 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

Cassie

20 days ago

Yeah, it's always something with Magento. Let's go with C and see if that fixes the issue.

upvoted 0 times

...

Sylvie

22 days ago

I agree, Magento can be quite tricky sometimes. I think C is the right option too.

upvoted 0 times

...

Jody

23 days ago

Yeah, I think you're right. Let's try that and see if it solves the issue.

upvoted 0 times

...

Walton

1 months ago

I agree, Magento can be quite tricky sometimes. I think specifying Elasticsearch in the Admin panel is the missing step.

upvoted 0 times

...

Mammie

2 months 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

2 months 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

2 months ago

I agree with Francine. Configuring Elasticsearch in the Magento Admin panel should solve the issue.

upvoted 0 times

...

Francine

2 months ago

I think the correct answer is C) Specify Elasticsearch as the search engine in the Magento Admin panel.

upvoted 0 times

...

Emogene

2 months 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

2 months ago

I agree with Paz. Configuring Elasticsearch in the Magento Admin panel should solve the issue.

upvoted 0 times

...

Paz

2 months ago

I think the correct answer is C) Specify Elasticsearch as the search engine in the Magento Admin panel.

upvoted 0 times

...