magento magento certified professional cloud developer practice test

You are migration 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 data loss?

• A. Configuration the mysql disk size using a variable in the , magento,evn,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 CU
• 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/ 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 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 oft JavaScript minification to reduce the build time.
Besides reducing the build phase time what two consequences does turning off JavaScript
minification have? Choose 2 answers

• 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

After deploying to Staging for the first time with the Fastly module installed, you notice that Fastly is
not caching pages. Page caching works properly in a local development environment.
What two steps are required to make Fastly cache pages?
Choose 2 answers

• A. Activate the module by setting Caching Application to Fastly CDN.
• B. Connect the Fastly shield using the Shield setting in the Magento admin.
• C. Enable the Fastly connection by running magento-Cloud fastly:setup.
• D. Populate VCL in Fastly by clicking on Upload VCL to Fastly in the Magento admin.

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, custom modules 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 –with-dependencies argument
• D. Remove magento.produce-enterprise-edition from the root composer, Json requirements and run composer update

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/ece-tools/src
• C. Run the command composer update magento/ece-tools
• D. Run the Command ece-tools self-upgrade

You are adding a new website to the Magento store you manage. This website will run on the same
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