Magento-Certified-Professional-Cloud-Developer Exam Questions Instant Access

Question 1

For the Magento search backend you would like lo move from MySQL lo 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?

AConfigure the relationships Section of the .magento.app.yaml file

BFind an appropriate Elasticsearch module to require with Composer

CSpecify Elasticsearch as the search engine in the Magento Admin panel

DRemove the MySQL service from the services. yaml file

Answer : A

Question 2

You created a custom module that is not functioning as expected on your Integration environment. You would like to debug the code using Xdebug. XdeDug is missing from the output of the command php -m

What are two ways to load the Xdebug module?

Choose 2 answers

ACreate a custom php.ini that includes the extension

BYou log a support request as php modules can only be installed by support

CAdd xdebug into the . magento. app. yaml file under the extensions section

DIn the phpserver folder. create a folder conf-d and add a file ext-xdebug.im that Includes the extension

Answer : B, C

Question 3

After contacting Magento Support you were advised to permanently enable the Redis disable_locking option.

How do you implement this on a Production environment?

AAdd disable_locking =true into the php.ini file in the Magento project root.

BModify the .magento,app,yaml file to add the REDIS_SESSION_CONFIGURATION environment variable.

CAdd the SESSION_CONFIGURATION environment variable into , magento,env,yaml with the correct value.

DIn app/etc./env.php,add disable_locking: True inside the Redis session configuration block.

Answer : C

Question 4

You migrated a live On-Premise application to Magento Commerce Cloud Pro. The performance on Staging and Production is fine However, the internal testing team notices overall performance degradation on the Integration environment

Why is this happening?

AThe Integration branch uses Platform-as-a-Service shared resources

BXdebug Is always enabled on the Integration branch

CThe Staging and Production environments are consuming all available resources

DThe Integration branch services have not been optimized In the .magento/services.yaml file

Answer : C

Question 5

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

AActivate the module by setting Caching Application to Fastly CDN.

BConnect the Fastly shield using the Shield setting in the Magento admin.

CEnable the Fastly connection by running magento-Cloud fastly:setup.

DPopulate VCL in Fastly by clicking on Upload VCL to Fastly in the Magento admin.

Answer : A, D

Question 6

You built a custom command that runs during the build phase, but it is not generating files property Magento Support provided a patch that you added to the project

What must you do to ensure this command runs after the patch has been applied?

AEnsure your custom command runs after the ece-tools build hooks

BMove your custom command to run in the deploy phase

CApply the patch manually in your custom command, because patches are always applied at the end of deployment

DNothing because patches are already applied when any hook runs

Answer : A

Question 7

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?

ARun bin/magento module: disable MyCompany_MyModule on the local environment and then commit and deploy the
app/etc/config.php file

BRun bin/magento module:disable MyCompany_MyModule on the production environment and download and commit the
app/etc/config.php file

CDelete the module from the git repository leaving the record in app/etc/config.php Intact and deploy the changes

DRemove the module line from the app/etc/config.php file on the local environment and then deploy the file

Answer : A

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