Summer Sale Limited Time 65% Discount Offer - Ends in 0d 00h 00m 00s - Coupon code: ecus65

Magento Magento-Certified-Professional-Cloud-Developer - Magento Certified Professional Cloud Developer Exam

Magento Magento-Certified-Professional-Cloud-Developer Premium Access     Download Demo    
Page: 1 / 2
Total 60 questions

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 usingmagento-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 are reviewing a third party extension for MagentoCommerce Cloudcompatibility 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 erc/frontend/di.xml file

D.

Direct instantiation of generated classes by the objectManager without the class being referenced in the constructor

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

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

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 are adding a new website tothe 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

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.

For the Magento search backend you would like lo move from MySQL lo Elasticsearch for your existing project.You have confirmed that your services. yamlfile 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 therelationships 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

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

The merchant wants to offer specific pricing in different currency markets so you have set up multiple websites to cover each currency.

Now they want customers to be directed to the appropriate website based on the country they are in.

Howdo you configure this?

A.

Use the Country Mapping in the Fastly settings to map country codes to store views

B.

In the Project Web UI. enable the Website IP Mapping setting

C.

Update magento-vars.php to detect the country code from the IP address and map it

D.

Build or install a Magento extension that changes the default currency code on applicationinit

You are debugging an issue with an extensionthat only occurs in Production.The extension writes relevant information using the debug log level

However that specific information is not getting written to the logs on Production

How do you fix this>

A.

Enable developer mode in Production for a short period to gather the required information

B.

Write a custom logger that writes the debug information to var/log/custom, log

C.

Enable debug logging in app/etc/config.php locally and deploy it to Production

D.

Enable debug logging in the Admin interface in Production

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 thelocal environment and then commitand 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