QUESTION: 25

You are reviewing a third party extension for Magento Commerce Cloud compatibility.
Which pattern makes a module incompatible with Magento Commerce Cloud?

Direct instantiation by the ObjectManager of non-generated classes in .phtml template files
Direct instantiation by the ObjectManager in non-constructor methods with the class also being referenced in the constructor signature
Configuration referencing generated Proxy classes in the modules etc/frontend/di.xml file
Direct instantiation of generated classes by the ObjectManager without the class being referenced in the constructor

Answer(s): B

Reveal Solution Next Question

You have a project deploying Static Content on the deploy phase. This process is optimized using the SCD_MATRIX configuration in the deploy stage of the .magento.env.yaml file. After moving the process to the build phase, Static Content Deployment is no longer optimized and all themes and all locales are generating.
How do you resolve this?

The SCD_MATRIX configuration is only used on the deploy phase
Add the --use_scd_matrix flag to the ece-tools build:generate command in the .magento.app.yaml file
Move the SCD_MATRIX configuration to the build stage of the .magento.env.yaml file
Configure the variable ENABLE_SCD_MATRIX in the .magento.env.yaml file

Answer(s): C

Reference:

https://devdocs.magento.com/cloud/deploy/static-content-deployment.html

Reveal Solution Next Question

QUESTION: 27

In a Pro plan project, you notice there is a mail delivery problem in the Integration environment. How do you troubleshoot this?

Change the log level in the log:email section of the .magento.env.yaml file
Update the SPF record in the DNS
Look in the var/log directory for the mail.log file
Move the test to the Staging environment

Answer(s): D

Reveal Solution Next Question

QUESTION: 28

You are reviewing a third party extension for Magento Commerce Cloud compatibility. You discover the module writes to a custom directory called internal/ within the Magento base directory.
The directory has to be shared by all web servers.
What do you do so the module can be used on Magento Commerce Cloud?

Create a symlink from /tmp/internal to the internal/ folder
Declare a shared mount for the internal/ directory in .magento.app.yaml
Request the vendor make the directory configurable in the Magento admin
Add a patch for extension so it uses the subdirectory var/internal/ instead

Answer(s): B

Reveal Solution Next Question

Free MAGENTO-CERTIFIED-PROFESSIONAL-CLOUD-DEVELOPER Exam Braindumps (page: 7)

QUESTION: 25

QUESTION: 26

Reference:

QUESTION: 27

QUESTION: 28