Cisco®
CompTIA
Checkpoint
ISC
EC-Council
EXIN
Fortinet
ITIL®
Juniper
PMI
Microsoft
VMware
Avaya
Google
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk®
Scrum
All Vendors
  2. Home
  3. Exams
  4. Magento
  5. MAGENTO-CERTIFIED-PROFESSIONAL-CLOUD-DEVELOPER

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

Page 5 of 16
PDF with 60 Questions

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 two.)

  1. Activate the module by setting Caching Application to Fastly CDN.
  2. Connect the Fastly shield using the Shield setting in the Magento admin.
  3. Enable the Fastly connection by running magento-cloud fastly:setup.
  4. Populate VCL in Fastly by clicking on Upload VCL to Fastly in the Magento admin.

Answer(s): A,D


Reference:

https://devdocs.magento.com/cloud/cdn/configure-fastly.html



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?

  1. Create a new project based on magento/project-enterprise-edition:2.3.0, then add ece-tools, custom modules and themes again with composer and migrate the data
  2. Run composer require magento/magento-cloud-metapackage:">=2.3.0 <2.3.1" --update-with-dependencies
  3. Revert the composer.json to the last commit before the update and run the command again with the --with-dependencies argument
  4. Remove magento/product-enterprise-edition from the root composer.json requirements and run composer update

Answer(s): C


Reference:

https://devdocs.magento.com/cloud/project/ece-tools-upgrade-project.html



Magento Support advises you to upgrade to the latest release of ece-tools matching the project’s Magento Commerce version 2.3.1. How do you do that?

  1. Require the exact version with composer require magento/ece-tools:2.3.1-pX where X is the latest release number
  2. Clone the repository github.com/magento/ece-tools and copy the src/ folder to vendor/magento/ece-tools/src
  3. Run the command composer update magento/ece-tools
  4. Run the command ece-tools self-upgrade

Answer(s): C


Reference:

https://devdocs.magento.com/cloud/project/ece-tools-update.html



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?

  1. Deploy an updated app/etc/config.php that includes the website URL.
  2. In the Project Web UI, add a separate branch for the new website, and set the URL in the appropriate branch variable.
  3. Deploy an updated magento-vars.php that maps the hostname to the website code.
  4. In the Project Web UI, add a JSON variable mapping website codes to URLs.

Answer(s): A






Post your Comments and Discuss Magento MAGENTO-CERTIFIED-PROFESSIONAL-CLOUD-DEVELOPER exam with other Community members: