Adobe Exam AD0-E706 Topic 12 Question 33 Discussion

Actual exam question for Adobe's AD0-E706 exam

Question #: 33
Topic #: 12

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?

AThe injected class logged to the exception log rile, but a different logging implementation is used during deployment

BFiles were written to the root Magento directory. which is read-only on Magento Commerce Cloud

CA connection to the database was attempted which Is not available during the build phase

DThe three webservers generated different content which causes the build to be rolled back for safety

Show Suggested Answer

Suggested Answer: C

by Lizette at May 20, 2024, 06:59 AM

Limited Time Offer

25%

Off

Get Premium AD0-E706 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Cassandra

1 months ago

I'm picturing the poor developer right now, scratching their head and trying to figure out why their code works locally but not in production. Classic Magento problems, am I right?

upvoted 0 times

Kristin

9 days ago

B) Files were written to the root Magento directory, which is read-only on Magento Commerce Cloud

upvoted 0 times

...

Shayne

24 days ago

C) A connection to the database was attempted which is not available during the build phase

upvoted 0 times

...

Marg

26 days ago

A) The injected class logged to the exception log file, but a different logging implementation is used during deployment

upvoted 0 times

...

Renato

2 months ago

Haha, the three webservers generating different content? That's a good one! I'll go with C, though. Seems like the most logical explanation.

upvoted 0 times

Hannah

17 days ago

A: Let's go with C then and see if that solves the issue.

upvoted 0 times

...

Yolando

1 months ago

B: I agree, C does seem like the most logical explanation for why the build phase is failing.

upvoted 0 times

...

Vincenza

1 months ago

A: Yeah, the three webservers generating different content does sound funny!

upvoted 0 times

...

Tracey

2 months ago

I'm going with A. The logging implementation is different during deployment, and that's causing the problem. Sneaky little thing, isn't it?

upvoted 0 times

...

Annmarie

2 months ago

Could it be that the database connection is not available during the build phase?

upvoted 0 times

...

Teri

2 months ago

Aha! It's gotta be B. Writing files to the root directory is a big no-no on Magento Commerce Cloud. That read-only file system is tripping you up.

upvoted 0 times

Kirk

1 months ago

C) A connection to the database was attempted which is not available during the build phase

upvoted 0 times

...

Joni

1 months ago

B) Files were written to the root Magento directory, which is read-only on Magento Commerce Cloud

upvoted 0 times

...

Cordie

1 months ago

A) The injected class logged to the exception log file, but a different logging implementation is used during deployment

upvoted 0 times

...

Arletta

1 months ago

A) The injected class logged to the exception log file, but a different logging implementation is used during deployment

upvoted 0 times

...

Felix

2 months ago

B) Files were written to the root Magento directory, which is read-only on Magento Commerce Cloud

upvoted 0 times

...

Jackie

2 months ago

A) The injected class logged to the exception log file, but a different logging implementation is used during deployment

upvoted 0 times

...

Gregoria

2 months ago

I agree with Hyman. Maybe the injected classes are causing conflicts during deployment.

upvoted 0 times

...

Tamala

2 months ago

Hmm, I'm guessing it's option C. The build phase doesn't have access to the database, so any database-related operations would cause issues.

upvoted 0 times

...

Hyman

2 months ago

I think the issue might be related to the injected Magento core classes.

upvoted 0 times

...