Instantly download AD0-E706 training test engine

After contacting Magento Support you were advised to permanently enable the Redis disable_locking option.
How do you implement this on a Production environment?

• A. Add disable_locking =true into thephp.ini file in the Magento project root.
• B. Modify the .magento,app,yaml file to add the REDIS_SESSION_CONFIGURATION environment variable.
• C. Add the SESSION_CONFIGURATION environment variable into , magento,env,yaml with the correct value.
• D. In app/etc./env.php,add disable_locking: True inside the Redis session configuration block.

You have a Starter project. Your code is ready for testing in the Staging environment, but you need the latest data from Production What do you do to update the Staging environment?

• A. Checkout the Production environment and use the magento-cloud syncCLI command
• B. Log in to the Project Web Ul. choose theStaging environment, and click Sync
• C. Checkout the Staging branch and use the git push origin -f command
• D. Log in to the Project Web Ul. choose the Staging environment, and click Merge

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?

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

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

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

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

• A. Put the composer credentials into/mnt/build/.config/composer/auth.json
• B. 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
• C. Add the composer_auth variable with the sensitive option enabled
• D. Add the env:coMPOSER_AUTH variable onthe project level and make it visible on the build phase