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

Adobe Exam AD0-E722 Topic 3 Question 35 Discussion

Actual exam question for Adobe's AD0-E722 exam
Question #: 35
Topic #: 3
[All AD0-E722 Questions]

An Adobe Commerce Architect creates a stopword for the Italian locale named stopwordsjtJT.csv and changes the stopword directory to the following: /app/code/Custovendor/Elasticsearch/etc/stopwords/

What is the correct approach to change the stopwords directory inside the custom module?

Show Suggested Answer Hide Answer
Suggested Answer: A, C

Option A is correct because enabling the config flag under deployment/blue_green/enabled is one of the steps to ensure zero downtime during the deployment process of Magento 2 on-premises. This flag enables the blue-green deployment feature, which allows deploying a new version of the Magento application to a separate environment (blue) without affecting the current live environment (green).Once the new version is ready, the traffic can be switched from green to blue with minimal or no downtime1.

Option C is correct because running bin/magento setup:upgrade --keep-generated is another step to ensure zero downtime during the deployment process of Magento 2 on-premises. This command updates the database schema and data without deleting the generated code and static view files.This way, the Magento application can still serve requests from the cache while the database is being upgraded2.

Option B is incorrect because running bin/magento setup:upgrade --dry-run=true does not upgrade the database, but only checks if there are any errors or conflicts in the database schema or data.This command can be used for testing purposes, but it does not affect the deployment process or the downtime3.

Option D is incorrect because there is no such option as --convert-old-scripts-true for the bin/magento setup:upgrade command. This option does not exist in Magento 2 and does not have any effect on the deployment process or the downtime.

Option E is incorrect because there is no such config flag as developer/zero_down_time/enabled in Magento 2. This flag does not exist in Magento 2 and does not have any effect on the deployment process or the downtime.


1: Blue-green deployment | Adobe Commerce Developer Guide

2: Deploy Magento to production | Adobe Commerce Developer Guide

3: Command-line installation options | Adobe Commerce Developer Guide

by Apolonia at Jan 28, 2025, 06:18 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel
Ashlyn
8 days ago
I hope the exam doesn't have any 'stop' signs for the correct answer!
upvoted 0 times
...
Cherry
9 days ago
Wait, we're talking about stopwords for the Italian locale? That's amore!
upvoted 0 times
...
Stefanie
12 days ago
I'm torn between options A and C. Both seem valid, but I'm leaning towards C because it's more elegant and doesn't require modifying the Stopwords class directly.
upvoted 0 times
...
Ryann
13 days ago
Option B seems a bit overkill, just to change the stopwords directory. Why bother with a setup patch when you can do it directly in the custom module?
upvoted 0 times
...
Amira
1 months ago
I agree with Frank. Option C looks like the most straightforward way to change the stopwords directory without having to modify the core configuration data.
upvoted 0 times
Eve
13 days ago
User 3: Option C does look like the most straightforward approach. Good call, Frank.
upvoted 0 times
...
Dominque
16 days ago
User 2: Yeah, I agree. It seems like the easiest way to change the stopwords directory.
upvoted 0 times
...
Gerald
20 days ago
User 1: I think Option C is the best choice.
upvoted 0 times
...
...
Frank
2 months ago
The correct approach seems to be option C. By adding the stopwords to the stopwordsDirectory parameter of the DirectoryBuilder class, the custom module will be automatically detected by Adobe Commerce.
upvoted 0 times
Herminia
16 days ago
Yeah, that makes sense. It will automatically detect the custom module.
upvoted 0 times
...
Joesph
26 days ago
I think option C is the way to go.
upvoted 0 times
...
...
Albert
2 months ago
Hmm, that makes sense too. It's important to ensure the stopwords are correctly configured within the custom module for effective search functionality.
upvoted 0 times
...
Daisy
2 months ago
I disagree, I believe we should add stopwords to the stopwordsDirectory and CustomerVendor_Elasticsearch to the stopwordsModule parameter of the \Magento\Elasticsearch\SearchAdapter\Query\Preprocessor\Stopwords Class Via di.xml.
upvoted 0 times
...
Albert
2 months ago
I think the correct approach is to add stopwords to the stopwordsDirectory parameter of the \Magento\Elasticsearch\Model\Adapter\Document\DirectoryBuilder Class Via stopwords/it.xml.
upvoted 0 times
...

Save Cancel