CompTIA
Checkpoint
ISC
HP
Dell
EC-Council
EXIN
Fortinet
ITIL®
Juniper
PMI
Microsoft
VMware
Avaya
Google
Salesforce
Amazon
Palo Alto Networks
Certiport
ISC2
All Vendors
  2. Home
  3. Exams
  4. Adobe
  5. AD0-E706

Free AD0-E706 Exam Braindumps (page: 5)

Page 4 of 16
PDF with 60 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?

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

Answer(s): A



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?

  1. 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
  2. Add the following variable on the Integration branch and set Its value to 86400 env:CONFIG_STORES_DEFAULT_ADMIN_SECURITY_SESSION_LIFETIME
  3. Run the following MagentoCLI command
    php bin/magento config:set admin/security/session_lifetime 86400
  4. On the Integration environment set the Admin Session Lifetime in the Magento admin backend under
    Stores > Configuration > Advanced > Admin > Security

Answer(s): B



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?

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

Answer(s): B



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?

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

Answer(s): A






Post your Comments and Discuss Adobe AD0-E706 exam with other Community members:

AD0-E706 Exam Discussions & Posts