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 fall.
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 logrile, 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
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, custommodules and themes again with composer and migrate the data
B. Run composer require magento/magento-cloud-metapakage:'' =2, 3.0 < 2, 3,1'' ?update-with dependencies
C. Revert the composer.join to the last commit before the update and run the command again with the 瓀 ith-dependencies argument
D. Remove magento.produce-enterprise-edition from the root composer, Json requirements and run composer update
You are going to create a backup of an Integration branch beforeimplementing some new feature What are two ways to create the backup of the integration branch? Choose 2 answers
A. Create a snapshot using the ece-tools snapshot:create command
B. Create a snapshot using the snapshot button In the Project Web Ul
C. Create a snapshot using the magento-cloud snapshot: create command
D. Submit a support ticket requesting a backup be made
Your project is in a phase where the locales that will be used are still being determined. You need toconfigure 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
B. Configure SCD_ON_DEMAND to true in the .magento.env.yaml file
C. 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. yarn! file
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 thephp.ini file in the Magento project root.
B. 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.
D. In app/etc./env.php,add disable_locking: True inside the Redis session configuration block.
You built a custom command that runs during the build phase, but it is not generating files property Magento Support provided a patch that you added to theproject.
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
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 oft JavaScript minification to reduce the build time.
Besides reducing the build phase time what two consequences does turning off JavaScript minification have? Choose 2 answers
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 tobe 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
In a Pro plan project, you notice there is amail delivery problem in the Integration environment. How do you troubleshoot this?
A. Change the log level in the lcg:emall 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
You add a new Composer dependency utilizing composer require. After testing composer install locally, you add the Composer local and Json files and perform a deployment. The build phase fails as Composer is unable to resolve the dependencies.
Why do 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
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
D. Build or install a Magento extension that changes the default currency code on application init