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

You are going to create a backup of an Integration branch before implementing some new feature What are two ways to create the backup of the integration branch?Choose 2 answers

• Create a snapshot using the ece-tools snapshot:create command
• Create a snapshot using the snapshot button In the Project Web Ul
• Create a snapshot using the magento-cloud snapshot: create command
• Submit a support ticket requesting a backup be made

You built a custom command that runs during the build phase, but it is not generating files property Magento Support provided a patch that you added to the projectWhat must you do to ensure this command runs after the patch has been applied?

• Ensure your custom command runs after the ece-tools build hooks
• Move your custom command to run in the deploy phase
• Apply the patch manually in your custom command, because patches are always applied at the end of deployment
• Nothing because patches are already applied when any hook runs

While launching a site migrated from Magento 1 you are instructed to change the website CNAME record in your DNS provider by Magento for go liveWhat is the purpose of setting this record9

• Setting this record causes sent email to be property authenticated and not show in junk folders
• Setting this record enables the page caching service for your site
• Setting this record is needed on Pro to allow upsizing servers without downtime
• Setting this record reduces the time it takes for customers to start seeing your Magento 2 site

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 executionThere are instances when the process gets locked after Production deployments and order data is not exported.How do you prevent this from happening'?

• Use the vas_iocks_clear variable available for the post_deploy stage in the .magento. env. yaml file
• Write a custom post_deploy hook to delete orphan lock tiles and include it in the .magento.app.yaml file
• Use the var_locks_clear variable available for the build stage In the . magento. app. yaml file
• You must access the Production environment and delete the lock file

Magento Support advises you lo upgrade to the latest release of ece-tools matching the project's Magento Commerce version 2 3 1 How do you do that?

• Require the exact version with composer require magento/ece-tools:2.3.1-px where X is the latest release number
• Clone the repository githab.com/magento/ece-tools and copy the ate/ folder to vendor/magento/ece-tools/src
• Run the command composer update magento/ece-tools
• Run the Command ece-tools self-upgrade

You need to disable a module on a Magento Commerce 2 3 Cloud project and remove its database tables The module uses the declarative schema system to manage its database changesWhich action do you take?

• Run bin/magento module: disable MyCompany_MyModule on the local environment and then commit and deploy the app/etc/config.php file
• Run bin/magento module:disable MyCompany_MyModule on the production environment and download and commit the app/etc/config.php file
• Delete the module from the git repository leaving the record in app/etc/config.php Intact and deploy the changes
• Remove the module line from the app/etc/config.php file on the local environment and then deploy the file

You need to get code with a backend order placement security related fix into production as quickly as possible.The project currently deploys static content during the build phase with both stags/global/SKIP_SCD and stage/deploy/STATIC_STATIC_CONTENT_SYMLINK set to false.What setting in .magento,env,yaml minimizes the overall deployment time?

• Remove all themes from stages/global/SCD_MATRIX so they will not be generated
• Set stage/global/Static_CONTENT_SYMLINK to true to symlink static assets to the init directory
• Set stage/global/SCD_COMPRESSION_LEVEL to 0 to avoid the compression overhead
• Set stage/global/SKIP_SCD to true to completely avoid static content processing

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

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 environmentHow do you configure the variable?

• Use the magento-cloud CLl utility with the environment inheritable and level flags
• Add the variable to the variables section under Project Settings specifying inheritance level
• Add the variable to the .magento.env.yaml file specifying the environment and inheritable
• Use vendor/bin/ece-tools to generate a local config.phpfile and commit the setting

You need to directly access the database that belongs to your Integration environment from your local environment How do you achieve this?

• Find the connection Information from the env.php file and connect with your local MySQL client
• Collect the SSH connection details using magento-cloud ssh --pipe and connect with your local MySQL client
• Add the ece-tools db-expose command to your deploy hook
• Use the magento-cloud db:sql command