Why does this occur?

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

Answer: A