← Back to exam page

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

Loading demo links...

Showing 7–9 of 10 questions

Question 7

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?

Select an option, then click Submit answer.

  • ○

    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
Question 8

You want to exclude some themes from static assets generation only for integration environments. You are trying to choose where to set the SCD_EXCLUDE_THEMES variable in the .magento.env.yaml file or in the Project Web UI.

What prevents the usage of the .magento.env.yaml file?

Select an option, then click Submit answer.

  • ○

    Child environments inherit the variable when you use the .magento.env.yaml file
  • ○

    The code from integration would be merged into the Staging and Production branches
  • ○

    The .magento.env.yaml file can contain only deployment configuration options, which are only available if static assets generation runs on the deploy phase
  • ○

    Only variables which are set using the Project Web UI has the option visible during build
Question 9

You are tasked to improve the user experience of the most visited product pages after deploying releases to Production. The aim is to reduce initial page load times.

How do you achieve this?

Select an option, then click Submit answer.

  • ○

    Create a custom build command and use CURL to cache the page
  • ○

    Use the Magento Admin to configure Fastly to cache the pages after deployment
  • ○

    Modify the post_deploy hook in the .magento.app.yaml file to include the URLs as arguments to the ece-tools command
  • ○

    Use the WARM_UP_PAGES variable in the .magento.env.yaml file to cache the pages during post_deploy