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

• A.Variables which are set using the Project Web Ul are not available on the build phase the admin password variable should be set in the . magento.env. yaml file
• B.The sensitive option is required for env:ADMIN PASSWORD variable
• C.Deploy scripts read configuration from the environment variablecalled magento_cloud_variables. which contains an array of variables which were set without the env: prefix
• D.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

Comment: *

Name: *

Email: *

Verification: *

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

• A.Five
• B.Ten
• C.Eight
• D.Fifteen

Comment: *

Name: *

Email: *

Verification: *

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

• A.In the QUEUE_ConFIGURATION variable added in the project Web UI or magento-cloud CLI In the env:QUEUE_CONFIGURATION variable added in the project Web UI ormagento Cloud CLI.
• B.In the app/etc/env.php file
• C.In the QUEUE_CONFIGURATION variable in the ,magento, env, yaml file

Comment: *

Name: *

Email: *

Verification: *

You need to install a third party extension which is provided in a tar archive It expands to a folder Structure in app/code/MyCompany/MyMedule.
Which action do you take to install the extension?

• A.Use the composer-merge-plugin to enable support for extension in app/code
• B.Use the composer package command to create a composer package and install it with composer require
• C.Add it to the project inapp/code and commit it to git
• D.Request composer repository credentials from the extension vendor

Comment: *

Name: *

Email: *

Verification: *

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 tile or in the Project WeD Ul.
What prevents the usage of the . magento. env.yaml file?

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

Comment: *

Name: *

Email: *

Verification: *