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.
Correct Answer:
Verified
Q2: A merchant using Magento Commerce Cloud Pro
Q3: A project has a Magento cron job
Q4: For the Magento search backend, you would
Q5: You are updating a Magento Commerce Cloud
Q6: You migrated a live On-Premise application to
Q8: You created a custom module that is
Q9: You add a new Composer dependency utilizing
Q10: On a project that deploys static content
Q11: You are tasked to improve the user
Q12: You are setting up a third-party integration
Unlock this Answer For Free Now!
View this answer and more for free by performing one of the following actions
Scan the QR code to install the App and get 2 free unlocks
Unlock quizzes for free by uploading documents