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: 4)

Page 3 of 16
PDF with 60 Questions

A merchant using Magento Commerce Cloud Pro reports an issue with an order missing transaction data. The application uses a payment gateway integration which posts a series of callbacks to Magento.

You would like to retrieve a complete list of calls to build a timeline of what happened.

How do you achieve this?

  1. Use the magento -cloud environment: logs command to retrieve the access. log file from Production
  2. Use SSH to access all nodes and investigate the access. leg riles
  3. Use the magento-cloud environment:ssh command to access the environment and investigate the access.log file
  4. View the access. logfile in the Project web UI

Answer(s): B



You added the env:ADMIN_PASSWORD variable in the Project Web Ul to change a Magento admin user's password After deployment you are unable to login using the new password.

What causes this?

  1. When you add a variable. the build stage is being skipped because the codebase has not been changed You must push a commit to trigger a full deploy
  2. Deploy scripts read configuration from the environment variablecalled magento_cloud_variables. which contains an array of variables which were set without the env: prefix
  3. Variables which are set using the Project Web Ul are not available on the build phase the admin password variable should be
    set in the . magento.env. yaml file
  4. The sensitive option is required for env:ADMIN PASSWORD variable

Answer(s): D



A custom module that adds a new console command for bin/magento has just been built Deploying this to the Production environment on your Pro plan site causes the build phase to fall.

You find this occurs when you inject certain Magento core classes in your console command class The command works on your local environment.

Why does this occur?

  1. The injected class logged to the exception logrile, but a different logging implementation is used during deployment
  2. Files were written to the root Magento directory. which is read-only on Magento Commerce Cloud
  3. A connection to the database was attempted which Is not available during the build phase
  4. The three webservers generated different content which causes the build to be rolled back for safety

Answer(s): A



You have created a new Integration branch and did not receive the administrator email with the password reset link. What is prohibiting the email from sending?

  1. You have not enabled the Magento Email module with bin/magento module: enable
  2. The Outgoing Emails setting is disabledunder Environment Settings in the Project Web Ul
  3. Email is always disabled on all integration branches
  4. You have not configured SendGrid tor this environment

Answer(s): C






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

AD0-E706 Exam Discussions & Posts