Free Magento-Certified-Professional-Cloud-Developer – Magento Certified Professional Cloud Developer Exam Practice Test Question

Select all that apply, then click Submit answer.

• ○

  Create a custom php.ini that includes the extension

• ○

  You log a support request as PHP modules can only be installed by support

• ○

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

• ○

  In the phpserver folder, create a folder conf.d and add a file ext-xdebug.ini that includes the extension
  
  

Select all that apply, then click Submit answer.

• ○

  Download and commit app/etc/config.php from production

• ○

  Run ece-tools scd-deploy:set build on production

• ○

  Run ece-tools config:dump on production

• ○

  Use scp to copy app/etc/config.php from local to production
  
  

Select all that apply, then click Submit answer.

• ○

  View the logs in the var/reports/ directory on the remote server

• ○

  View the exception.log file in the var/log/ directory

• ○

  View the deploy.log file in the /var/log/ directory

• ○

  View the cloud.log file in the var/log/ directory
  
  

Select all that apply, then click Submit answer.

• ○

  Create a snapshot using the ece-tools snapshot:create command

• ○

  Create a snapshot using the snapshot button in the Project Web UI

• ○

  Create a snapshot using the magento-cloud snapshot:create command

• ○

  Submit a support ticket requesting a backup be made
  
  

Select all that apply, then click Submit answer.

• ○

  Activate the module by setting Caching Application to Fastly CDN.

• ○

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

• ○

  Enable the Fastly connection by running magento-cloud fastly:setup.

• ○

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

Select an option, then click Submit answer.

• ○

  Setting this record causes sent email to be properly authenticated and not show in junk folders.

• ○

  Setting this record enables the page caching service for your site.

• ○

  Setting this record is needed on Pro to allow upsizing servers without downtime.

• ○

  Setting this record reduces the time it takes for customers to start seeing your Magento 2 site.
  
  

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
  
  

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
  
  

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
  
  

Select an option, then click Submit answer.

• ○

  The build phase runs on a separate server and variables are not available there, you must keep the credentials in the auth.json file, but you can replace the password with its hash

• ○

  Add the env:COMPOSER_AUTH variable on the project level and make it visible on the build phase

• ○

  Put the composer credentials into /mnt/build/.config/composer/auth.json

• ○

  Add the COMPOSER_AUTH variable with the sensitive option enabled