You are adding a new website to the Magento store you manage. This website will run on thesame instance of Magento to take advantage of shared integration processes.

When accessing the new website URL. it redirects to the original website. The files in /media/ and /static/

do not redirect The correct URL is present in the website configuration.

What step must you complete for the URL to stop redirecting?

A. Deploy an updated app/etc/config.php that includes the website URL.

B. In the Project Web Ul, add a separate branch for the new website and set the URL in the appropriate branch variable

C. Deploy an updated magento-vars. php that maps the hostname to the website code

D. in the Project Web Ul, add a JSON variable mapping website codes to URLs

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

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 need to specify the admin password using an environment variable.

You have created an environment variable env:ADMIN_PASSWORD with a valid password When

attempting to log in to the Magento Admin it is not accepting the new password.

How do you correct the environment variable?

A. The Sensitive option is checked by default and must be disabled

B. The env:ADMIN_PASSWORD variable can only be used for an initial installation

C. The environment variable should not havethe env: prefix

D. The ADMIN_PASSWORD variable Should be Configured Via .magento.env.yaml

Your client is expecting a five-day sale where the traffic will approximately double. Your instance is consuming all available resources onall three nodes so upsizing one level is appropriate.

How many upsize days will this event use?

A. Five

B. Eight

C. Ten

D. Fifteen

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

A client has an in-house design team which manages content on their Magento Commerce Cloudproject

This content is rapidly changing and they would like the ability to maintain their own stylesheets in a

structured way without affecting site uptime.

How do you achieve this on the integration branch?

A. Modify the writeable directories on the Integration Environment by using the . magento. env. yaml file

B. Add a custom command to the build hook in the .magento. app. yaml file to retrieve the stylesheets from a client hosted location

C. The Magento Infrastructure Team needs to create a writeable directory in which the stylesheets can be uploaded.

D. Use the, magento, app, yaml file to create a mount in the pub directory

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 need to disable a module on a Magento Commerce 2 3 Cloud project and remove its database tables The module usesthe declarative schema system to manage its database changes.

Which action do you take?

A. Run bin/magento module: disable MyCompany_MyModule on the local environment and then commit and deploy the app/etc/config.php file

B. Run bin/magento module:disable MyCompany_MyModule on the production environment and download and commit the app/etc/config.php file

C. Delete the module from the git repository leaving the record in app/etc/config.php Intact and deploy the changes

D. Remove the module line from the app/etc/config.php file on the local environment and then deploy the file