Online Access Free Magento-Certified-Professional-Cloud-Developer Practice Test

You are testing an integration to an external service that requires you to configure an accesskey in an environment variable.You created a new environment to validate the functionality The variable must only impact this environment How do you configure the variable?

• A.Use the magento-cloud CLl utility with the environment inheritable and level flags
• B.Add the variable to the .magento.env.yamlfile specifying the environment and inheritable
• C.Add the variable to the variables section under Project Settings specifying inheritance level
• D.Use vendor/bin/ece-tools to generate a local config.phpfile and commit the setting

A merchant slates 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 to be reduced?

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

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.Run the command bin/magento setup:hotfix:apply --patch=m2-hctfixes/extension-fix.patch
• B.Commit the patch because the pre-commit hook will abort the commitit any hotfix causes an issue
• C.Configure a deploy hook in .magento.app.yamlthat executes
  vendor/bin/ece-tools hotfix:apply -dry-run
• D.Run the command git apply m2-hotfixea/extension-fix.patch

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 the Integration environment set the Admin Session Lifetime in the Magento admin backend under Stores > Configuration > Advanced > Admin > Security
• B.Run the following Magento CLI command
  php bin/magento config:set admin/security/session_lifetime 86400
• C.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/ confi.php file and commit this file
• D.Add the following variable on the Integration branch and set Its value to 86400 env:CONFIG_STORES_DEFAULT_ADMIN_SECURITY_SESSION_LIFETIME

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, the add eco-tools, custom modules and themes again with composer and migrate the data
• B.Revert the composer.join to the last commit before the update and run the command again with the
  -with-dependencies argument
• C.Remove magento.produce-enterprise-edition from the root composer, Json requirements and run composer update
• D.Run composer require magento/magento-cloud-metapakage:'' =2, 3.0 < 2, 3,1'' - update-with dependencies