While setting up a Magento project you run the following command
magento-cloud variable:update ADMIN_USERNAME -value=alice
What will this command do?

• A. Change your username to alice tor logging into the magento-cloud CLl tool C.
• B. Change the username of the default administrator account to alice
• C. Update the Magento cloud/admin/username config variable to alice
• D. Configure the Magento Commerce Cloud tools to use alice for API call authentication

You are updating a Magento Commerce Cloud project from version 2.2.5 to 2.3.0 with the command Composer require magento/product-enterprise-edition:2,3,0 However, composer is unable to complete the task because the installed version of magento/magento-cloud-metapackage is not compatible.
How do you upgrade magento to the desired version?

• A. Revert the composer.join to the last commit before the update and run the command again with the
  -with-dependencies argument
• B. Create a new project based on magento/ project-enterprise-edition: 2, 3, 0, the add eco-tools, custommodules and themes again with composer and migrate the data
• C. Remove magento.produce-enterprise-edition from the root composer, Json requirements and run composer update
• D. Run composer require magento/magento-cloud-metapakage:'' =2, 3.0 < 2, 3,1'' - update-with dependencies

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

You are setting up a third-party integration only for the Production environment, which connects to anexternal RabbitMQ server.
Where do you put the configuration?

• A. In the app/etc/env.php file
• B. In the QUEUE_ConFIGURATION variable added in the project Web UI or magento-cloud CLI In the env:QUEUE_CONFIGURATION variable added in the project Web UI ormagento Cloud CLI.
• C. In the QUEUE_CONFIGURATION variable in the ,magento, env, yaml file

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 live What is the purpose of setting this record9

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