Deck 5: Magento Certified Professional Cloud Developer

Question 1

Your client is expecting a five-day sale where the traffic will approximately double. Your instance is consuming all available resources on all three nodes so upsizing one level is appropriate. How many upsize days will this event use?

A) Five
B) Eight
C) Ten
D) Fifteen

Answer 1

Five

Question 2

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 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 Use SSH to access all nodes and investigate the files
C) Use the magento-cloud environment:ssh command to access the environment and investigate the access.log file magento-cloud environment:ssh command to access the environment and investigate the file
D) View the access.log file in the Project Web UI View the file in the Project Web UI

Answer 2

View the access.log file in the Project Web UI View the file in the Project Web UI

Question 3

A project has a Magento cron job implemented to export new order data to a file. This process can also be triggered by a custom bin/magento command. The functionality uses a lock file in var/locks to prevent concurrent execution. There are instances when the process gets locked after Production deployments and order data is not exported. How do you prevent this from happening?

A) Use the VAR_LOCKS_CLEAR variable available for the post_deploy stage in the .magento.env.yaml file Use the VAR_LOCKS_CLEAR variable available for the post_deploy stage in the .magento.env.yaml file
B) Write a custom post_deploy hook to delete orphan lock files and include it in the .magento.app.yaml file Write a custom hook to delete orphan lock files and include it in the .magento.app.yaml file
C) Use the VAR_LOCKS_CLEAR variable available for the build stage in the .magento.app.yaml file variable available for the build stage in the
D) You must access the Production environment and delete the lock file

Answer 3

Use the VAR_LOCKS_CLEAR variable available for the post_deploy stage in the .magento.env.yaml file Use the VAR_LOCKS_CLEAR variable available for the post_deploy stage in the .magento.env.yaml file

Question 4

For the Magento search backend, you would like to move from MySQL to Elasticsearch for your existing project. You have confirmed that your services.yaml file is configured appropriately. However, after your most recently deployment, you notice the search engine is still set to MySQL. What additional step must be completed?

A) Configure the relationships section of the .magento.app.yaml file Configure the relationships section of the .magento.app.yaml file
B) Find an appropriate Elasticsearch module to require with Composer
C) Specify Elasticsearch as the search engine in the Magento Admin panel
D) Remove the MySQL service from the services.yaml file Remove the MySQL service from the

Question 5

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?

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

Question 6

You migrated a live On-Premise application to Magento Commerce Cloud Pro. The performance on Staging and Production is fine. However, the internal testing team notices overall performance degradation on the Integration environment. Why is this happening?

A) The Integration branch uses Platform-as-a-Service shared resources
B) Xdebug is always enabled on the Integration branch
C) The Staging and Production environments are consuming all available resources
D) The Integration branch services have not been optimized in the .magento/services.yaml file The Integration branch services have not been optimized in the .magento/services.yaml file

Question 7

A custom module that adds a new console command for bin/magento has just been built. Deploying this to the Production environment on your Pro plan site causes the build phase to fail. You find this occurs when you inject certain Magento core classes in your console command class. The command works on your local environment. Why does this occur?

A) The injected class logged to the exception log file, but a different logging implementation is used during deployment.
B) Files were written to the root Magento directory, which is read-only on Magento Commerce Cloud.
C) A connection to the database was attempted, which is not available during the build phase.
D) The three webservers generated different content, which causes the build to be rolled back for safety.

Question 8

You created a custom module that is not functioning as expected on your Integration environment. You would like to debug the code using Xdebug. Xdebug is missing from the output of the command php -m . What are two ways to load the Xdebug module? (Choose two.)

A) Create a custom php.ini that includes the extension Create a custom php.ini that includes the extension
B) You log a support request as PHP modules can only be installed by support
C) Add xdebug into the .magento.app.yaml file under the extensions section Add xdebug into the .magento.app.yaml file under the extensions section
D) In the phpserver folder, create a folder conf.d and add a file ext-xdebug.ini that includes the extension In the phpserver folder, create a folder conf.d and add a file ext-xdebug.ini that includes the extension

Question 9

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 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 You did not execute the install locally with --require-dev

Question 10

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

A) The deploy artifact size will be decreased because of the larger JavaScript can be symlinked
B) Browsing the store will be slower because larger JavaScript files have to be downloaded
C) The deploy phase will be shorter because JavaScript can be symlinked from init instead of copied
D) The build phase will be longer because the additional pass of JavaScript merging

Question 11

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?

A) Create a custom build command and use CURL to cache the page
B) Use the Magento Admin to configure Fastly to cache the pages after deployment
C) Modify the post_deploy hook in the .magento.app.yaml file to include the URLs as arguments to the ece-tools command Modify the post_deploy hook in the .magento.app.yaml file to include the URLs as arguments to the ece-tools command
D) Use the WARM_UP_PAGES variable in the .magento.env.yaml file to cache the pages during post_deploy Use the WARM_UP_PAGES variable in the .magento.env.yaml file to cache the pages during

Question 12

You are setting up a third-party integration only for the Production environment, which connects to an external RabbitMQ server. Where do you put the configuration?

A) In the app/etc/env.php file In the app/etc/env.php file
B) In the QUEUE_CONFIGURATION variable added in the Project Web UI or magento-cloud CLI QUEUE_CONFIGURATION variable added in the Project Web UI or magento-cloud CLI
C) In the env:QUEUE_CONFIGURATION variable added in the Project Web UI or magento-cloud CLI env:QUEUE_CONFIGURATION
D) In the QUEUE_CONFIGURATION variable in the .magento.env.yaml file variable in the .magento.env.yaml

Question 13

You have a Starter project. Your code is ready for testing in the Staging environment, but you need the latest data from Production. What do you do to update the Staging environment?

A) Log in to the Project Web UI, choose the Staging environment, and click Sync
B) Log in to the Project Web UI, choose the Staging environment, and click Merge
C) Checkout the Staging branch and use the git push origin -f command Checkout the Staging branch and use the git push origin -f command
D) Checkout the Production environment and use the magento-cloud sync CLI command Checkout the Production environment and use the magento-cloud sync CLI command

Question 14

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.

Question 15

You are upgrading a project to the latest version of Magento Commerce Cloud and part of the process involves a PHP version upgrade. This is now ready to be tested by the QA Team on the Integration environment. How do you apply the PHP version upgrade?

A) Change the PHP version in the .magento.app.yaml file and re-deploy Change the PHP version in the .magento.app.yaml file and re-deploy
B) SSH into the Integration environment and upgrade PHP manually
C) Change the PHP_VERSION configuration in the .magento.env.yaml file and re-deploy Change the PHP_VERSION configuration in the .magento.env.yaml
D) Use the magento-cloud CLI tool to update the PHP_VERSION variable Use the magento-cloud CLI tool to update the variable

Question 16

You built a custom command that runs during the build phase, but it is not generating files properly. Magento Support provided a patch that you added to the project. What must you do to ensure this command runs after the patch has been applied?

A) Ensure your custom command runs after the ece-tools build hooks.
B) Move your custom command to run in the deploy phase.
C) Apply the patch manually in your custom command, because patches are always applied at the end of deployment.
D) Nothing, because patches are already applied when any hook runs.

Question 17

Your team is working on two major changes affecting the product page and you want the ability to implement and test these changes in parallel. Your company is using the Pro plan How do you achieve this using the Project Web UI?

A) Create branches from Production to ensure the catalog is up to date
B) Create branches from Integration to facilitate merging
C) Create branches from the Magento Cloud Docker image to ensure the changes are made on the most recent codebase
D) Create branches from Staging to ensure the changes are tested on an environment similar to Production

Question 18

You are reviewing a third party extension for Magento Commerce Cloud compatibility. You discover the module writes to a custom directory called internal/ within the Magento base directory. The directory has to be shared by all web servers. What do you do so the module can be used on Magento Commerce Cloud?

A) Create a symlink from /tmp/internal to the internal/ folder Create a symlink from /tmp/internal to the folder
B) Declare a shared mount for the internal/ directory in .magento.app.yaml Declare a shared mount for the internal/ directory in .magento.app.yaml
C) Request the vendor make the directory configurable in the Magento admin
D) Add a patch for extension so it uses the subdirectory var/internal/ instead Add a patch for extension so it uses the subdirectory var/internal/ instead

Question 19

You need to disable a module on a Magento Commerce 2.3 Cloud project and remove its database tables. The module uses the declarative schema system to manage its database changes. Which action do you take?

A) Run bin/magento module:disable MyCompany_MyModule on the local environment and then commit and deploy the app/et?/config.php file Run bin/magento module:disable MyCompany_MyModule on the local environment and then commit and deploy the app/et?/config.php file
B) Run bin/magento module:disable MyCompany_MyModule on the production environment and download and commit the app/etc/config.php file on the production environment and download and commit the app/etc/config.php
C) Delete the module from the git repository leaving the record in app/etc/config.php intact and deploy the changes Delete the module from the git repository leaving the record in intact and deploy the changes
D) Remove the module line from the app/etc/config.php file on the local environment and then deploy the file Remove the module line from the file on the local environment and then deploy the file

Question 20

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 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 Configure the mysql disk size in the .magento/services.yaml

Question 21

A merchant states the downtime during the deployment phase is too long. After analysis, it is determined the static content deployment is the longest process. Static content needs to be available immediately after deployment. How can the static content deployment time be reduced?

A) Move static content deploy to the build phase
B) Commit var/view_preprocessed to git so it already exists during the deployment phase Commit var/view_preprocessed to git so it already exists during the deployment phase
C) Set stage/global/SKIP_SCD to true Set stage/global/SKIP_SCD to true
D) Reduce the number of store views per website

Question 22

You fixed an issue in a third-party extension using a patch named m2-hotfixes/extension-fix.patch . Before committing the patch to the repository you want to test it locally. How do you test a patch in a clean working copy?

A) Commit the patch because the pre-commit hook will abort the commit if any hotfix causes an issue
B) Run the command git apply m2-hotfixes/extension-fix.patch Run the command git apply
C) Run the command bin/magento setup:hotfix:apply --patch=m2-hotfixes/extension-fix.patch Run the command bin/magento setup:hotfix:apply --patch=m2-hotfixes/extension-fix.patch
D) Configure a deploy hook in .magento.app.yaml that executes vendor/bin/ece-tools hotfix:apply --dry-run Configure a deploy hook in .magento.app.yaml that executes vendor/bin/ece-tools hotfix:apply --dry-run

Question 23

You upgraded an integration branch in your Magento Commerce Cloud project, but received an error during the deploy phase. What are the two ways to review details about the deployment? (Choose two.)

A) View the logs in the var/reports/ directory on the remote server View the logs in the var/reports/ directory on the remote server
B) View the exception.log file in the var/log/ directory View the exception.log file in the var/log/ directory
C) View the deploy.log file in the /var/log/ directory deploy.log /var/log/
D) View the cloud.log file in the var/log/ directory cloud.log

Question 24

You need to specify the admin password using an environment variable. You have created an environment variable env:ADMIN_PASSWORD with a valid password. When attempting to log in to the Magento Admin it is not accepting the new password. How do you correct the environment variable?

A) The Sensitive option is checked by default and must be disabled
B) The env:ADMIN_PASSWORD variable can only be used for an initial installation The variable can only be used for an initial installation
C) The environment variable should not have the env: prefix The environment variable should not have the env: prefix
D) The ADMIN_PASSWORD variable should be configured via .magento.env.yaml ADMIN_PASSWORD variable should be configured via .magento.env.yaml

Question 25

You need to increase the Admin Session Lifetime up to 86400 seconds for the branch named Integration and children branches, but not for the Staging and Production branches. How do you update this on the Integration branch and its child branches?

A) On your local environment, set the Admin Session Lifetime in the Magento admin backend under Stores > Configuration > Advanced > Admin > Security then dump this setting into the app/etc/config.php file and commit this file On your local environment, set the Admin Session Lifetime in the Magento admin backend under Stores > Configuration > Advanced > Admin > Security
B) Add the following variable on the Integration branch and set its value to 86400: env:CONFIG_STORES_DEFAULT_ADMIN_SECURITY_SESSION_LIFETIME
C) Run the following Magento CLI command: php bin/magento config:set admin/security/session_lifetime 86400
D) On the Integration environment, set the Admin Session Lifetime in the Magento admin backend under Stores > Configuration > Advanced > Admin > Security On the Integration environment, set the Admin Session Lifetime in the Magento admin backend under

Question 26

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 file?

A) Child environments inherit the variable when you use the .magento.env.yaml file Child environments inherit the variable when you use the .magento.env.yaml file
B) The code from integration would be merged into the Staging and Production branches
C) The .magento.env.yaml file can contain only deployment configuration options, which are only available if static assets generation runs on the deploy phase The file can contain only deployment configuration options, which are only available if static assets generation runs on the deploy phase
D) Only variables which are set using the Project Web UI has the option visible during build

Question 27

The merchant wants to offer specific pricing in different currency markets, so you have set up multiple websites to cover each currency. Now they want customers to be directed to the appropriate website based on the country they are in. How do you configure this?

A) Use the Country Mapping in the Fastly settings to map country codes to store views.
B) In the Project Web UI, enable the Website IP Mapping setting.
C) Update magento-vars.php to detect the country code from the IP address and map it. Update magento-vars.php to detect the country code from the IP address and map it.
D) Build or install a Magento extension that changes the default currency code on application init.

Question 28

After contacting Magento Support, you were advised to permanently enable the Redis disable_locking option. How do you implement this on a Production environment?

A) Add disable_locking = true into the php.ini file in the Magento project root. Add disable_locking = true into the php.ini file in the Magento project root.
B) Modify the .magento.app.yaml file to add the REDIS_SESSION_CONFIGURATION environment variable. Modify the .magento.app.yaml file to add the REDIS_SESSION_CONFIGURATION environment variable.
C) Add the SESSION_CONFIGURATION environment variable into .magento.env.yaml with the correct value. Add the SESSION_CONFIGURATION environment variable into .magento.env.yaml with the correct value.
D) In app/etc/env.php , add disable_locking: 1 inside the Redis session configuration block. In app/etc/env.php , add disable_locking: 1 inside the Redis session configuration block.

Question 29

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. 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. 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. Use the file to create a mount in the pub directory.

Question 30

You want to improve the ability to monitor Production deployments by setting up an email notification system. How do you achieve this?

A) Enable Deployment Notifications under Configure Environment > Settings in the Project Web UI
B) Build a custom module which hooks into the deployment phase and sends emails in real-time
C) Configure log notifications in the .magento.env.yaml file Configure log notifications in the .magento.env.yaml file
D) Use the magento-cloud environment:deploy:email command to enable email notifications Use the magento-cloud environment:deploy:email command to enable email notifications

Question 31

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

Question 32

You need to directly access the database that belongs to your Integration environment from your local environment. How do you achieve this?

A) Find the connection information from the env.php file and connect with your local MySQL client Find the connection information from the env.php file and connect with your local MySQL client
B) Collect the SSH connection details using magento-cloud ssh --pipe and connect with your local MySQL client Collect the SSH connection details using magento-cloud ssh --pipe and connect with your local MySQL client
C) Add the ece-tools db-expose command to your deploy hook Add the ece-tools db-expose command to your deploy hook
D) Use the magento-cloud db:sql command Use the magento-cloud db:sql command

Question 33

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?

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

Question 34

You are going to create a backup of an Integration branch before implementing some new feature. What are two ways to create the backup of the Integration branch? (Choose two.)

A) Create a snapshot using the ece-tools snapshot:create command Create a snapshot using the ece-tools snapshot:create command
B) Create a snapshot using the snapshot button in the Project Web UI
C) Create a snapshot using the magento-cloud snapshot:create command magento-cloud snapshot:create
D) Submit a support ticket requesting a backup be made

Question 35

You need to test a data-related issue occurring on your Production environment. You replicate the data to your staging environment utilizing the Synchronization tool. When you access your staging environment, you are redirected to your Production environment. Your project is on the Starter plan. How do you prevent the redirect?

A) Use the magento-cloud route:add command to create a route to the Staging URL Use the magento-cloud route:add command to create a route to the Staging URL
B) Modify the MAGENTO_CLOUD_ROUTES environment variable on your staging environment Modify the MAGENTO_CLOUD_ROUTES environment variable on your staging environment
C) Enter the proper URL in the Routes for Staging under the Environment Settings in the Project Web UI
D) Configure UPDATE_URLS to true in the .magento.env.yaml file Configure UPDATE_URLS to true in the .magento.env.yaml file

Question 36

To secure composer credentials you want to remove the auth.json file from the project repository. How do you do that?

A) 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 The build phase runs on a separate server and variables are not available there, you must keep the credentials in the file, but you can replace the password with its hash
B) Add the env:COMPOSER_AUTH variable on the project level and make it visible on the build phase Add the env:COMPOSER_AUTH variable on the project level and make it visible on the build phase
C) Put the composer credentials into /mnt/build/.config/composer/auth.json Put the composer credentials into /mnt/build/.config/composer/auth.json
D) Add the COMPOSER_AUTH variable with the sensitive option enabled COMPOSER_AUTH variable with the sensitive option enabled

Question 37

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?

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

Question 38

Exploring the Production environment, you find MYSQL_USE_SLAVE_CONNECTION is enabled. What is the purpose of this setting?

A) To split the database tables between the three Production servers and improve performance.
B) To enable fault tolerance on the MySQL cluster.
C) To utilize the read-only slave servers and improve the overall performance.
D) To allow database backups from a MySQL slave server with minimal impact on the Production site.

Question 39

After making changes to custom commands in the deploy and build phases, you deploy to Staging. The deployment takes much longer than expected, and Staging is in maintenance mode for most of this time. What do you do to reduce site downtime?

A) Set the SKIP_MAINTENANCE_SCD variable to true in the . magento.env.yaml file. Set the SKIP_MAINTENANCE_SCD variable to true in the . magento.env.yaml file.
B) Add a custom command to the post_deploy phase to activate deferred deployment.
C) Move custom commands from the deploy phase to the build phase.
D) Update the SCD_MATRIX variable to include only necessary custom commands. Update the SCD_MATRIX variable to include only necessary custom commands.

Question 40

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 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 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 The sensitive option is required for variable

Question 41

You need to get code with a backend order placement security related fix into production as quickly as possible. The project currently deploys static content during the build phase with both stage/global/SKIP_SCD and stage/deploy/STATIC_CONTENT_SYMLINK set to false . What setting in magento.env.yaml minimizes the overall deployment time?

A) Remove all themes from stage/global/SCD_MATRIX so they will not be generated Remove all themes from stage/global/SCD_MATRIX so they will not be generated
B) Set stage/global/STATIC_CONTENT_SYMLINK to true to symlink static assets to the init directory Set stage/global/STATIC_CONTENT_SYMLINK to true to symlink static assets to the init directory
C) Set stage/global/SCD_COMPRESSION_LEVEL to 0 to avoid the compression overhead stage/global/SCD_COMPRESSION_LEVEL 0 to avoid the compression overhead
D) Set stage/global/SKIP_SCD to true to completely avoid static content processing to completely avoid static content processing

Question 42

You have created a new Integration branch and did not receive the administrator email with the password reset link. What is prohibiting the email from sending?

A) You have not enabled the Magento Email module with bin/magento module:enable You have not enabled the Magento Email module with bin/magento module:enable
B) The Outgoing Emails setting is disabled under Environment Settings in the Project Web UI
C) Email is always disabled on all integration branches
D) You have not configured SendGrid for this environment

Question 43

Your project is in a phase where the locales that will be used are still being determined. You need to configure your project in a manner that will allow them to be changed dynamically. How can you accomplish this?

A) Remove the system/default/general/locale configuration from the app/etc/config.php file Remove the system/default/general/locale configuration from the app/etc/config.php file
B) Configure SCD_ON_DEMAND to true in the .magento.env.yaml file Configure SCD_ON_DEMAND to true in the .magento.env.yaml
C) Run the command vendor/bin/ece-tools locales:unlock on the environment Run the command vendor/bin/ece-tools locales:unlock on the environment
D) Configure DYNAMIC_LOCALES in the SCD_MATRIX to true in the .magento.env.yaml file DYNAMIC_LOCALES SCD_MATRIX file

Question 44

A merchant with three websites using en_GB, fr_FR and de_AT requires a change in locale to de_DE for the German Production website. After running the following command on Production you notice the frontend design of the German website is broken: php bin/magento config:set --scope=websites --scope-code=german general/locale/code de_DE Static content deployment is set up on the deploy phase. Why did this happen?

A) Static Content is not pre-generated for the de_DE locale Static Content is not pre-generated for the locale
B) de_DE is not writeable in pub/static and has to be configured via the . magento.app.yaml file is not writeable in pub/static and has to be configured via the . magento.app.yaml file
C) The magento-cloud environment:deploy command has not been run yet to generate static content for the new locale The magento-cloud environment:deploy command has not been run yet to generate static content for the new locale
D) STATIC_CONTENT_SYMLINK is not configured in the .magento.env.yaml file STATIC_CONTENT_SYMLINK is not configured in the .magento.env.yaml