MAGENTO-CERTIFIED-PROFESSIONAL-CLOUD-DEVELOPER Online Practice Questions and Answers

You are migrating an existing Magento 2 website to Magento Commerce Cloud. After setting up the project you would like to migrate the database to the Integration branch. The database import fails with a disk space error.

How do you migrate the database without data loss?

A. Configure the mysql disk size using a variable in the .magento.env.yaml file

B. Open a Magento Support ticket to increase the Integration branch disk size

C. Trim down the database to a smaller size

D. Configure the mysql disk size in the .magento/services.yaml file

Magento Commerce Cloud comes with a variety of additional features that sets it apart from the on-premise Magento Commerce and Magento Open Source platforms.

What feature improves the release update process and simplifies commands to create a backup of the database, apply custom patches, and verify environment configuration?

A. Docker environment

B. Magento Cloud-specific CLI

C. Cloud configuration wizards

D. ECE-Tools package

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/ config.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 Magento CLI 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 a technical admin on a Magento Commerce Cloud account. A coworker needs to submit a support request with Magento Support.

What is needed to enable support ticket access?

A. Ask the account owner to add the user to shared access.

B. Ask the launch manager to create a support account for this user.

C. Change the environment access role to contributor for this user.

D. Update the project role of this user to administrator.

You are upgrading a project to the latest version of Magento Commerce Cloud and part of the process involves a PHP version upgrade. This is now ready to be tested by the QA Team on the Integration environment.

How do you apply the PHP version upgrade?

A. Change the PHP version in the .magento.app.yaml file and re-deploy

B. SSH into the Integration environment and upgrade PHP manually

C. Change the PHP_VERSION configuration in the .magento.env.yaml file and re-deploy

D. Use the magento-cloud CLI tool to update the PHP_VERSION variable

On a project that deploys static content during the build phase, a merchant states the deploy phase is still taking too long. You consider turning off JavaScript minification to reduce the build time.

Besides reducing the build phase time, what two consequences does turning off JavaScript minification have? (Choose two.)

A. The deploy artifact size will be decreased because of the larger JavaScript can be symlinked

B. Browsing the store will be slower because larger JavaScript files have to be downloaded

C. The deploy phase will be shorter because JavaScript can be symlinked from init instead of copied

D. The build phase will be longer because the additional pass of JavaScript merging

Magento Support advises you to 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 github.com/magento/ece-tools and copy the src/ 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 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 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 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 the magento-cloud CLI utility with the environment, inheritable and level flags

B. Add the variable to the variables section under Project Settings specifying inheritance level

C. Add the variable to the .magento.env.yaml file specifying the environment and inheritable

D. Use vendor/bin/ece-tools to generate a local config.php file and commit the setting