Magento MAGENTO-CERTIFIED-PROFESSIONAL-CLOUD-DEVELOPER Online Practice Questions and Exam Preparation

Magento MAGENTO-CERTIFIED-PROFESSIONAL-CLOUD-DEVELOPER Online Questions & Answers

• Question 51:

  A client has an in-house design team which manages content on their Magento Commerce Cloud project. This content is rapidly changing and they would like the ability to maintain their own stylesheets in a structured way without affecting site uptime.

  How do you achieve this on the Integration branch?

  A. Modify the writeable directories on the Integration Environment by using the .magento.env.yaml file.
  B. Add a custom command to the build hook in the .magento.app.yaml file to retrieve the stylesheets from a client hosted location.
  C. The Magento Infrastructure Team needs to create a writable directory in which the stylesheets can be uploaded.
  D. Use the .magento.app.yaml file to create a mount in the pub directory.
  D. Use the .magento.app.yaml file to create a mount in the pub directory.

• Question 52:

  You added the env:ADMIN_PASSWORD variable in the Project Web UI to change a Magento admin user's password. After deployment you are unable to login using the new password. What causes this?

  A. When you add a variable, the build stage is being skipped, because the codebase has not been changed. You must push a commit to trigger a full deploy
  B. Deploy scripts read configuration from the environment variable called $MAGENTO_CLOUD_VARIABLES, which contains an array of variables which were set without the env: prefix
  C. Variables which are set using the Project Web UI are not available on the build phase, the admin password variable should be set in the .magento.env.yaml file
  D. The sensitive option is required for env:ADMIN_PASSWORD variable
  C. Variables which are set using the Project Web UI are not available on the build phase, the admin password variable should be set in the .magento.env.yaml file

• Question 53:

  You are migrating an existing Magento 2 website to Magento Commerce Cloud. After setting up the project you would like to migrate the database to the Integration branch. The database import fails with a disk space error. How do you migrate the database without data loss?

  A. Configure the mysql disk size using a variable in the .magento.env.yaml file
  B. Open a Magento Support ticket to increase the Integration branch disk size
  C. Trim down the database to a smaller size
  D. Configure the mysql disk size in the .magento/services.yaml file
  D. Configure the mysql disk size in the .magento/services.yaml file

• Question 54:

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

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

• Question 55:

  You add a new Composer dependency utilizing composer require. After testing composer install locally, you add the Composer lock and json files and perform a deployment. The build phase fails as Composer is unable to resolve the dependencies.

  Why did this happen?

  A. The versions of PHP on your local environment and integration environment differ
  B. Your commit needs to contain the updated vendor folder
  C. The project cache should have been cleared with the magento-cloud:project-build-cache command
  D. You did not execute the install locally with --require-dev
  A. The versions of PHP on your local environment and integration environment differ

• Question 56:

  While launching a site migrated from Magento 1, you are instructed to change the website CNAME record in your DNS provider by Magento for go live. What is the purpose of setting this record?

  A. Setting this record causes sent email to be properly authenticated and not show in junk folders.
  B. Setting this record enables the page caching service for your site.
  C. Setting this record is needed on Pro to allow upsizing servers without downtime.
  D. Setting this record reduces the time it takes for customers to start seeing your Magento 2 site.
  D. Setting this record reduces the time it takes for customers to start seeing your Magento 2 site.

• Question 57:

  A merchant using Magento Commerce Cloud Pro reports an issue with an order missing transaction data. The application uses a payment gateway integration which posts a series of callbacks to Magento.

  You would like to retrieve a complete list of calls to build a timeline of what happened.

  How do you achieve this?

  A. Use the magento-cloud environment:logs command to retrieve the access.log file from Production
  B. Use SSH to access all nodes and investigate the access.log files
  C. Use the magento-cloud environment:ssh command to access the environment and investigate the access.log file
  D. View the access.log file in the Project Web UI
  D. View the access.log file in the Project Web UI

• Question 58:

  In a Pro plan project, you notice there is a mail delivery problem in the Integration environment. How do you troubleshoot this?

  A. Change the log level in the log:email section of the .magento.env.yaml file
  B. Update the SPF record in the DNS
  C. Look in the var/log directory for the mail.log file
  D. Move the test to the Staging environment
  D. Move the test to the Staging environment

• Question 59:

  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?

  A. The SCD_MATRIX configuration is only used on the deploy phase
  B. Add the --use_scd_matrix flag to the ece-tools build:generate command in the .magento.app.yaml file
  C. Move the SCD_MATRIX configuration to the build stage of the .magento.env.yaml file
  D. Configure the variable ENABLE_SCD_MATRIX in the .magento.env.yaml file
  C. Move the SCD_MATRIX configuration to the build stage of the .magento.env.yaml file

• Question 60:

  You added a grunt autoprefixer command, which adds CSS vendor prefixes like -webkit- and -moz- to CSS files generated by the setup:static-content:deploy command.

  After deployment you still see CSS files without prefixes. The hooks section in the .magento.app.yaml file is:

  hooks: build: | npm install grunt autoprefixer php ./vendor/bin/ece-tools build:generate php ./vendor/bin/ece-tools build:transfer deploy: | php ./vendor/bin/ece-tools deploy

  Considering static assets are being generated on the build phase, why are CSS prefixes missing?

  A. Custom commands can be run only on the deploy phase
  B. CSS vendor prefixes must be added to CSS files locally and committed as part of a theme
  C. The static assets were not generated yet when the grunt command ran
  D. The custom command was run before static assets were transferred into the init directory
  B. CSS vendor prefixes must be added to CSS files locally and committed as part of a theme