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

A client has an in-house design team which manages content on their Magento Commerce Cloud project. 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 writable 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 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

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

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

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 UI, 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 UI, add a JSON variable mapping website codes to URLs.

You are going to create a backup of an Integration branch before implementing some new feature.

What are two ways to create the backup of the Integration branch? (Choose two.)

A. Create a snapshot using the ece-tools snapshot:create command

B. Create a snapshot using the snapshot button in the Project Web UI

C. Create a snapshot using the magento-cloud snapshot:create command

D. Submit a support ticket requesting a backup be made

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

Which pattern makes a module incompatible with Magento Commerce Cloud?

A. Direct instantiation by the ObjectManager of non-generated classes in .phtml template files

B. Direct instantiation by the ObjectManager in non-constructor methods with the class also being referenced in the constructor signature

C. Configuration referencing generated Proxy classes in the modules etc/frontend/di.xml file

D. Direct instantiation of generated classes by the ObjectManager without the class being referenced in the constructor

For the Magento search backend, you would like to move from MySQL to 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. Specify Elasticsearch as the search engine in the Magento Admin panel

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

A custom module that adds a new console command for bin/magento has just been built. Deploying this to the Production environment on your Pro plan site causes the build phase to fail.

You find this occurs when you inject certain Magento core classes in your console command class. The command works on your local environment.

Why does this occur?

A. The injected class logged to the exception log file, but a different logging implementation is used during deployment.

B. Files were written to the root Magento directory, which is read-only on Magento Commerce Cloud.

C. A connection to the database was attempted, which is not available during the build phase.

D. The three webservers generated different content, which causes the build to be rolled back for safety.

A merchant with three websites using en_GB, fr_FR and de_AT requires a change in locale to de_DE for the German Production website. After running the following command on Production you notice the frontend design of the German website is broken:

php bin/magento config:set --scope=websites --scope-code=german general/locale/code de_DE

Static content deployment is set up on the deploy phase.

Why did this happen?

A. Static Content is not pre-generated for the de_DE locale

B. de_DE is not writeable in pub/static and has to be configured via the .magento.app.yaml file

C. The magento-cloud environment:deploy command has not been run yet to generate static content for the new locale

D. STATIC_CONTENT_SYMLINK is not configured in the .magento.env.yaml file