Free Adobe Certified Expert-Magento Commerce Cloud Developer Exam AD0-E706 Exam Practice Test

You want to exclude some themes from static assets generation only for integration environments You are trying to choose where to set the scd_exclude_themes variable in the . magento.env.yaml tile or in the Project WeD Ul.What prevents the usage of the . magento. env.yaml file?

• Child environments inherit the variable when you use the . magento. env. yaml file
• The code from integration would be merged into the Staging and Production branches
• The .magento.env.yama file can contain only deployment configuration options, which are only available it static assets generation runs on the deploy phase
• Only variables which are set using the Project Web Ul has the option visible during build

You are a technical admin on a Magento Commerce Cloud account A coworker needs to submit a support request with MagentoSupportWhat is needed to enable support ticket access'?

• Ask the account owner to add the user to shared access
• Ask the launch manager to create a support account for this user
• Change the environment access role to contributor for this user
• Update the project role of this user to administrator

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?

• Set the SKIP_MAINTENANCE_SCD variable to true In the . magento. env. yaml file
• Add a custom command to the post_deploy phase to activate deferred deployment
• Move custom commands from the deploy phase to the build phase.
• Update the SCD_MATRIX variable to include only necessary custom commands

You are tasked to improve the user experience of the most visited product pages after deploying releases to Production. The aim is to reduce initial page load times.How do you achieve this?

• Create a custom build command and use CURL to cache the page
• Use the Magento Admin to configure Fastly to cache the pages after deployment
• Modify the post_deploy hook in the .magento.app.yaml file to include the URLs as arguments to the ece-tools command
• Use the warm_up_PAGES variable in the .magento.env.yaml file to cache the pages during postdeploy

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

• Change the log level in the lcg:emall section of the .magento.env.yaml file
• Update the SPF record in the DNS
• Look In the var/log directory for the mail. log file
• Move the test to the Staging environment

Your company decided too move a Magento store to a subdomain https://shop.coinpany.ccm/ and redirect traffic from the old URL httpa://company.com/ to the new one. Your company is using the Starter plan.How do you implement the redirect?

• Configure a rewrite rule In the . htaccess file In the pub folder
• Submit a support ticket to add the redirect on the web-server level
• Add a route using the MANGENTO_CLOUD_ROUTES environment variable.
• Add a route Into the .magento/routes, yaml configuration file

On a project that deploys static content during the build phase a merchant states the deploy phase Is still taking too long You consider turning oft JavaScript minification to reduce the build time.Besides reducing the build phase time what two consequences does turning off JavaScript minification have? Choose 2 answers

• The deploy artifact size will be decreased because of the larger JavaScript can be symlinked
• Browsing the store will be slower because larger JavaScript files have to be downloaded
• The deploy phase will be shorter because JavaScript can be symlinked from init instead of copied
• The build phase will be longer because the additional pass of JavaScript merging

To secure composer credentials you want to remove the auch. Json file from the project repository How do you do that?

• The build phase runs on a separate server and variables are not available there you must keep the credentials in the auth. j son file, but you can replace the password with its hash
• Add the env:coMPOSER_AUTH variable on the project level and make it visible on the build phase
• Put the composer credentials into/mnt/build/.config/composer/auth.json
• Add the composer_auth variable with the sensitive option enabled

You want to improve the ability to monitor Production deployments by setting up an email notification system How do you achieve this?

• Enable Deployment Notifications under Configure Environment > Settings in the Protect Web
• Build a custom module which hooks into the deployment phase and sends emails in real-time
• Configure log notifications in the .magento.env.yaml file
• Use the magento-cloud environment:deploy:email command to enable email notifications

Your project is in a phase where the locales that will be used are still being determined. You need to configure your project in a manner that will allow them to be changed dynamicallyHow can you accomplish this?

• Remove the system/default/general/locale configuration from the app/etc/config.php file
• Configure SCD_ON_DEMAND to true in the .magento.env.yaml file
• Run the command vendor/bin/ece-tools locales:unlock on the environment
• Configure DYNAMIC_LOCALES in the SCD_MATRIX to true in the . magento. env. yarn! file