Adobe AD0-E706 Exam Questions Instant Access

Question 1

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?

AOn 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

BAdd the following variable on the Integration branch and set Its value to 86400
env:CONFIG_STORES_DEFAULT_ADMIN_SECURITY_SESSION_LIFETIME

CRun the following Magento CLI command
php bin/magento config:set admin/security/session_lifetime 86400

DOn the Integration environment set the Admin Session Lifetime in the Magento admin backend under
Stores > Configuration > Advanced > Admin > Security

Answer : B

Question 2

You are testing an integration to an external service that requires you to configure an access key in an environment variable. You created a new environment to validate the functionality The variable must only impact this environment

How do you configure the variable?

AUse the magento-cloud CLl utility with the environment inheritable and level flags

BAdd the variable to the variables section under Project Settings specifying inheritance level

CAdd the variable to the .magento.env.yaml file specifying the environment and inheritable

DUse vendor/bin/ece-tools to generate a local config.phpfile and commit the setting

Answer : B

Question 3

After making changes lo custom commands in the deploy and build phases you deploy to Staging. The deployment takes much longer than expected, and Staging is in maintenance mode tor most of this time.

What do you do to reduce site downtime?

ASet the SKIP_MAINTENANCE_SCD variable to true In the . magento. env. yaml file

BAdd a custom command to the post_deploy phase to activate deferred deployment

CMove custom commands from the deploy phase to the build phase.

DUpdate the SCD_MATRIX variable to include only necessary custom commands

Answer : C

Question 4

A project has a Magento cron job implemented to export new order data to a file. This process can also be triggered by a custom bin/magento command. The functionality uses a lock file in var/locks to prevent concurrent execution

There are instances when the process gets locked after Production deployments and order data is not exported.

How do you prevent this from happening'?

AUse the vas_iocks_clear variable available for the post_deploy stage in the .magento. env. yaml file

BWrite a custom post_deploy hook to delete orphan lock tiles and include it in the .magento.app.yaml file

CUse the var_locks_clear variable available for the build stage In the . magento. app. yaml file

DYou must access the Production environment and delete the lock file

Answer : B

Question 5

In a Pro plan project, you notice there is a mail delivery problem in the Integration environment How do you troubleshoot this?

AChange the log level in the lcg:emall section of the .magento.env.yaml file

BUpdate the SPF record in the DNS

CLook In the var/log directory for the mail. log file

DMove the test to the Staging environment

Answer : D

Question 6

You are debugging an issue with an extension that only occurs in Production. The extension writes relevant information using the debug log level

However that specific information is not getting written to the logs on Production

How do you fix this>

AEnable developer mode in Production for a short period to gather the required information

BWrite a custom logger that writes the debug information to var/log/custom, log

CEnable debug logging in app/etc/config.php locally and deploy it to Production

DEnable debug logging in the Admin interface in Production

Answer : D

Question 7

You are adding a new website to the Magento store you manage. This website will run on the same instance of Magento to take advantage of shared integration processes.

When accessing the new website URL. it redirects to the original website. The files in /media/ and /static/ do not redirect The correct URL is present in the website configuration

What step must you complete for the URL to stop redirecting?

ADeploy an updated app/etc/config.php that includes the website URL.

BIn the Project Web Ul, add a separate branch for the new website and set the URL in the appropriate branch variable

CDeploy an updated magento-vars. php that maps the hostname to the website code

Din the Project Web Ul, add a JSON variable mapping website codes to URLs

Answer : C

Adobe Certified Expert-Magento Commerce Cloud Developer AD0-E706 Exam Questions