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 enables the page caching service for your site

C. Setting this record is needed on Pro to allow upsizing servers without downtime

D. Setting this record reduces the time it takes for customers to start seeing your Magento 2 site

You have created a new Integration branch and did not receive the administrator email with the password reset link. What is prohibiting the email from sending?

A. You have not enabled the Magento Email module with bin/magento module: enable

B. The Outgoing Emails setting is disabledunder Environment Settings in the Project Web Ul

C. Email is always disabled on all integration branches

D. You have not configured SendGrid tor this environment

For the Magento search backend you would like lo move from MySQL lo Elasticsearch for your existing project. You have confirmed that your services. yaml file is configured appropriately However, after your most recently deployment, you notice the search engine is still set to MySQL.

What additional step must be completed?

A. Configure the relationships Section of the .magento.app.yaml file

B. Find an appropriate Elasticsearch module to require with Composer

C. SpecifyElasticsearch as the search engine in the Magento Admin panel

D. Remove the MySQL service from the services. yaml file

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?

A. On 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

B. Add the following variable on the Integration branch and set Its value to 86400 env:CONFIG_STORES_DEFAULT_ADMIN_SECURITY_SESSION_LIFETIME

C. Run the following MagentoCLI command php bin/magento config:set admin/security/session_lifetime 86400

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

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. 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

B. Run composer require magento/magento-cloud-metapakage:'' =2, 3.0 < 2, 3,1'' ?update-with dependencies

C. Revert the composer.join to the last commit before the update and run the command again with the 瓀 ith-dependencies argument

D. Remove magento.produce-enterprise-edition from the root composer, Json requirements and run composer update

You are reviewing a third party extension for Magento Commerce Cloud compatibility.

You discover the module writes to a custom directory called internal/ within the Magento base directory.

The directory has to be shared by all web servers.

What do you do so the module can be used on Magento Commerce Cloud?

A. Create a symlink from /top/internal to the internal/ folder

B. Declare a shared mount for the internal/directory in .magento. app.yaml

C. Request the vendor make the directory configurable in the Magento admin

D. Add a patch for extension so it uses the subdirectory var/internal/ instead

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?

A. Require the exact version with composer require magento/ece-tools:2.3.1-px where X is the latest release number

B. Clone the repository githab.com/magento/ece-tools and copy the ate/folder to vendor/magento/ecetools/src

C. Run the command composer update magento/ece-tools

D. Run the Command ece-tools self-upgrade

You want to improve the ability to monitor Production deployments by setting up an email notification system.

How do you achieve this?

A. Enable Deployment Notifications under Configure Environment > Settings in the Protect Web

B. Build a custom module which hooks into the deployment phase and sends emails in real-time

C. Configure log notifications in the.magento.env.yaml file

D. Use the magento-cloud environment:deploy:email command to enable email notifications

You need to directly access the database that belongs to your Integration environment from your local environment.

How do you achieve this?

A. Find the connection Information from the env.php file and connect with your local MySQL client

B. Collect the SSH connection details using magento-cloud ssh --pipe and connect with your local MySQL client

C. Add the ece-tools db-expose command to your deploy hook

D. Use the magento-cloud db:sql command

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?

A. Remove all themes from stages/global/SCD_MATRIX so they will not be generated

B. Set stage/global/Static_CONTENT_SYMLINK to true to symlink static assets to the init directory

C. Set stage/global/SCD_COMPRESSION_LEVEL to 0 to avoid the compression overhead

D. Set stage/global/SKIP_SCD to true to completely avoid static content processing