QUESTION: 13

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?

Configure the relationships Section of the .magento.app.yaml file
Find an appropriate Elasticsearch module to require with Composer
SpecifyElasticsearch as the search engine in the Magento Admin panel
Remove the MySQL service from the services. yaml file

Answer(s): A

Reveal Solution Next Question

QUESTION: 14

You need to increase the Admin Session Lifetime up to 86400 seconds for the branch named Integration and children branches but not for the Staging and Production branches.

How do you update this on the integration branch and its child branches?

On your local environment, set the Admin Session Lifetime In the Magento admin backend under
Stores> Configuration> Advanced > Admin >Security then dump this setting into the app /etc/ confi.php file and commit this file
Add the following variable on the Integration branch and set Its value to 86400 env:CONFIG_STORES_DEFAULT_ADMIN_SECURITY_SESSION_LIFETIME
Run the following MagentoCLI command
php bin/magento config:set admin/security/session_lifetime 86400
On the Integration environment set the Admin Session Lifetime in the Magento admin backend under
Stores > Configuration > Advanced > Admin > Security

Answer(s): B

Reveal Solution Next Question

QUESTION: 15

You fixed an issue in a third-party extension using a patch named m2-hotfixes/extension- fix.patch Before committing the patch to the repository you want to test itlocally.

How do you test a patch in a clean working copy?

Commit the patch because the pre-commit hook will abort the commit it any hotfix causes an issue
Run the command git apply m2-hotfixea/extension-fix.patch
Run the command bin/magento setup:hotfix:apply --patch=m2-hctfixes/extension- fix.patch
Configure a deploy hook in .magento.app.yaml that executes vendor/bin/ece-tools hotfix:apply --dry-run

Answer(s): B

Reveal Solution Next Question

QUESTION: 16

A merchant with three websites using en_GB. fr_FR and de_AT requires a change in locale to de_DE for the German Production website After running the following command on Production you notice the frontend design of the German website is broken:

Php bin/magento config:set scope=websites scopes code=germ general /local./code de_DE

Static content deployment is set up toon the deploy phase.

Why did this happen?

Static Content is not pre-generated for the de_DE locale
de_DE is not writeable in pub/static and has to be configured via the .magento.app.yaml file
The magento-cloud environment: deploy command has not been run yet to generate static content for the new locale
STA"IC_CONTENT_SYKLINK is not Configured in the .magento.env.yaml file

Answer(s): A

Reveal Solution Next Question

Free AD0-E706 Exam Braindumps (page: 4)

QUESTION: 13

QUESTION: 14

QUESTION: 15

QUESTION: 16