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. Log in to the Project Web UI, choose the Staging environment, and click Sync

B. Log in to the Project Web UI, choose the Staging environment, and click Merge

C. Checkout the Staging branch and use the git push origin -f command

D. Checkout the Production environment and use the magento-cloud sync CLI command

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 have the env: prefix

D. The ADMIN_PASSWORD variable should be configured via .magento.env.yaml

You are setting up a third-party integration only for the Production environment, which connects to an external 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

C. In the env:QUEUE_CONFIGURATION variable added in the Project Web UI or magento-cloud CLI

D. In the QUEUE_CONFIGURATION variable in the .magento.env.yaml file

A merchant using Magento Commerce Cloud Pro reports an issue with an order missing transaction data. The application uses a payment gateway integration which posts a series of callbacks to Magento.

You would like to retrieve a complete list of calls to build a timeline of what happened.

How do you achieve this?

A. Use the magento-cloud environment:logs command to retrieve the access.log file from Production

B. Use SSH to access all nodes and investigate the access.log files

C. Use the magento-cloud environment:ssh command to access the environment and investigate the access.log file

D. View the access.log file in the Project Web UI

You need to test a data-related issue occurring on your Production environment. You replicate the data to your staging environment utilizing the Synchronization tool. When you access your staging environment, you are redirected to your Production environment. Your project is on the Starter plan.

How do you prevent the redirect?

A. Use the magento-cloud route:add command to create a route to the Staging URL

B. Modify the MAGENTO_CLOUD_ROUTES environment variable on your staging environment

C. Enter the proper URL in the Routes for Staging under the Environment Settings in the Project Web UI

D. Configure UPDATE_URLS to true in the .magento.env.yaml file

A merchant states the downtime during the deployment phase is too long. After analysis, it is determined the static content deployment is the longest process. Static content needs to be available immediately after deployment.

How can the static content deployment time be reduced?

A. Move static content deploy to the build phase

B. Commit var/view_preprocessed to git so it already exists during the deployment phase

C. Set stage/global/SKIP_SCD to true

D. Reduce the number of store views per website

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 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/et/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

You added the env:ADMIN_PASSWORD variable in the Project Web UI to change a Magento admin user's password. After deployment you are unable to login using the new password.

What causes this?

A. When you add a variable, the build stage is being skipped, because the codebase has not been changed. You must push a commit to trigger a full deploy

B. Deploy scripts read configuration from the environment variable called $MAGENTO_CLOUD_VARIABLES, which contains an array of variables which were set without the env: prefix

C. Variables which are set using the Project Web UI are not available on the build phase, the admin password variable should be set in the .magento.env.yaml file

D. The sensitive option is required for env:ADMIN_PASSWORD variable

You added a grunt autoprefixer command, which adds CSS vendor prefixes like -webkit- and -moz- to CSS files generated by the setup:static-content:deploy command.

After deployment you still see CSS files without prefixes. The hooks section in the .magento.app.yaml file is:

hooks: build: | npm install grunt autoprefixer php ./vendor/bin/ece-tools build:generate php ./vendor/bin/ece-tools build:transfer deploy: | php ./vendor/bin/ece-tools deploy

Considering static assets are being generated on the build phase, why are CSS prefixes missing?

A. Custom commands can be run only on the deploy phase

B. CSS vendor prefixes must be added to CSS files locally and committed as part of a theme

C. The static assets were not generated yet when the grunt command ran

D. The custom command was run before static assets were transferred into the init directory

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 disabled under Environment Settings in the Project Web UI

C. Email is always disabled on all integration branches

D. You have not configured SendGrid for this environment