Nest 0 Cart
Nest Account
Popular Exams
All Categories...
Nest
Nest 0
Contact
Log In / Sign Up
Copyright 2024 © store. All rights reserved.
Home Magento Magento Certified Professional Cloud Developer

Magento Magento Certified Professional Cloud Developer Exam Practice Questions (P. 4)

  • Full Access (60 questions)
  • Six months of Premium Access
  • Access to one million comments
  • Seamless ChatGPT Integration
  • Ability to download PDF files
  • Anki Flashcard files for revision
  • No Captcha & No AdSense
  • Advanced Exam Configuration
Get Contributor Access
Question #16
On a project that deploys static content during the build phase, a merchant states the deploy phase is still taking too long. You consider turning off JavaScript minification to reduce the build time.
Besides reducing the build phase time, what two consequences does turning off JavaScript minification have? (Choose two.)
  1. A
    The deploy artifact size will be decreased because of the larger JavaScript can be symlinked
  2. B
    Browsing the store will be slower because larger JavaScript files have to be downloaded
  3. C
    The deploy phase will be shorter because JavaScript can be symlinked from init instead of copied
  4. D
    The build phase will be longer because the additional pass of JavaScript merging

Correct Answer:
AD

Question #17
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. A
    Activate the module by setting Caching Application to Fastly CDN.
  2. B
    Connect the Fastly shield using the Shield setting in the Magento admin.
  3. C
    Enable the Fastly connection by running magento-cloud fastly:setup.
  4. D
    Populate VCL in Fastly by clicking on Upload VCL to Fastly in the Magento admin.

Correct Answer:
AD
Reference:
https://devdocs.magento.com/cloud/cdn/configure-fastly.html

Question #18
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. A
    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. B
    Run composer require magento/magento-cloud-metapackage:">=2.3.0 <2.3.1" --update-with-dependencies
  3. C
    Revert the composer.json to the last commit before the update and run the command again with the --with-dependencies argument
  4. D
    Remove magento/product-enterprise-edition from the root composer.json requirements and run composer update

Correct Answer:
C
Reference:
https://devdocs.magento.com/cloud/project/ece-tools-upgrade-project.html

Question #19
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. A
    Require the exact version with composer require magento/ece-tools:2.3.1-pX where X is the latest release number
  2. B
    Clone the repository github.com/magento/ece-tools and copy the src/ folder to vendor/magento/ece-tools/src
  3. C
    Run the command composer update magento/ece-tools
  4. D
    Run the command ece-tools self-upgrade

Correct Answer:
C
Reference:
https://devdocs.magento.com/cloud/project/ece-tools-update.html

Question #20
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. A
    Deploy an updated app/etc/config.php that includes the website URL.
  2. B
    In the Project Web UI, add a separate branch for the new website, and set the URL in the appropriate branch variable.
  3. C
    Deploy an updated magento-vars.php that maps the hostname to the website code.
  4. D
    In the Project Web UI, add a JSON variable mapping website codes to URLs.

Correct Answer:
A

Previous Questions Next Questions

All Pages