New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Adobe AD0-E706 Exam - Topic 9 Question 46 Discussion

Actual exam question for Adobe's AD0-E706 exam
Question #: 46
Topic #: 9
[All AD0-E706 Questions]

You are reviewing a third party extension for Magento Commerce Cloud compatibility

You discover the module writes to a custom directory called internal/ within the Magento base directory

The directory has to be shared by all web servers

What do you do so the module can be used on Magento Commerce Cloud?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

0/2000 characters
Anisha
3 months ago
Just declare the shared mount, it's the best practice!
upvoted 0 times
...
Stephane
3 months ago
Definitely need to patch it to avoid issues.
upvoted 0 times
...
Corinne
3 months ago
Surprised they didn't make it configurable from the start!
upvoted 0 times
...
Nan
4 months ago
I disagree, a symlink might work too.
upvoted 0 times
...
Arlean
4 months ago
Option B is the way to go! Shared mounts are essential.
upvoted 0 times
...
Yuki
4 months ago
I lean towards option D because patching the extension to use a different directory seems like it could solve the problem, but I’m not sure if it’s the most efficient way.
upvoted 0 times
...
Shawn
4 months ago
I practiced a question similar to this, and I think making the directory configurable in the admin could be a good solution, but I’m not confident it’s the best approach here.
upvoted 0 times
...
Edgar
4 months ago
I'm not entirely sure, but I feel like creating a symlink could cause issues with file access across servers. Maybe option A isn't the best?
upvoted 0 times
...
Emerson
5 months ago
I remember something about shared mounts being important for compatibility in cloud environments, so I think option B might be the right choice.
upvoted 0 times
...
Lili
5 months ago
This is a tricky one. I'm leaning towards option B, but I want to make sure I understand the implications of using a shared mount before I commit to that.
upvoted 0 times
...
Adell
5 months ago
Option D looks like the best approach to me. Modifying the extension to use the var/internal/ directory instead of the custom one would be the cleanest solution.
upvoted 0 times
...
Rene
5 months ago
Hmm, I'm a bit unsure about this one. I'm not super familiar with Magento Commerce Cloud, so I'll have to think through the options carefully.
upvoted 0 times
...
Gwen
5 months ago
This seems like a straightforward question. I'd go with option B and declare a shared mount for the internal/ directory in the .magento.app.yaml file.
upvoted 0 times
...
Kirby
5 months ago
I think option A with the symlink could work, but I'm not sure if that's the recommended approach for Magento Commerce Cloud. I'll have to double-check the documentation.
upvoted 0 times
...
Jaleesa
1 year ago
B) Definitely go with the shared mount option. Trying to create a symlink or request a vendor change sounds like way too much hassle for a cloud deployment.
upvoted 0 times
...
Hubert
1 year ago
I'm not sure about option B, maybe we should also consider option D) Add a patch for extension so it uses the subdirectory var/internal/ instead
upvoted 0 times
...
Michell
1 year ago
This question is a real head-scratcher. I'd hate to be the one responsible for figuring this out - it sounds like a pain in the backend!
upvoted 0 times
Chara
1 year ago
D) Add a patch for extension so it uses the subdirectory var/internal/ instead
upvoted 0 times
...
Melissia
1 year ago
C) Request the vendor make the directory configurable in the Magento admin
upvoted 0 times
...
Lashaun
1 year ago
B) Declare a shared mount for the internal/directory in .magento. app.yaml
upvoted 0 times
...
Carylon
1 year ago
A) Create a symlink from /top/internal to the internal/ folder
upvoted 0 times
...
...
Lacey
1 year ago
D) Using the var/internal/ subdirectory instead of a custom location is a good idea. It keeps things more standardized and less likely to cause issues on the cloud platform.
upvoted 0 times
Wilbert
1 year ago
D) Add a patch for extension so it uses the subdirectory var/internal/ instead
upvoted 0 times
...
Shalon
1 year ago
B) Declare a shared mount for the internal/directory in .magento. app.yaml
upvoted 0 times
...
Harley
1 year ago
A) Create a symlink from /top/internal to the internal/ folder
upvoted 0 times
...
...
Harrison
1 year ago
I agree with Kenneth, option B sounds like the best solution to ensure compatibility with Magento Commerce Cloud
upvoted 0 times
...
Chauncey
1 year ago
B) Declaring a shared mount for the internal/ directory in .magento.app.yaml seems like the way to go. That's the recommended approach for handling shared directories in Magento Commerce Cloud.
upvoted 0 times
Mariann
1 year ago
D) Adding a patch for the extension to use the subdirectory var/internal/ is another possible fix
upvoted 0 times
...
Layla
1 year ago
C) Requesting the vendor to make the directory configurable in the Magento admin might be a good solution
upvoted 0 times
...
Mira
1 year ago
A) Creating a symlink from /top/internal to the internal/ folder could work too
upvoted 0 times
...
Louann
1 year ago
B) Declaring a shared mount for the internal/ directory in .magento.app.yaml is the best option
upvoted 0 times
...
...
Kenneth
1 year ago
I think we should go with option B) Declare a shared mount for the internal/directory in .magento.app.yaml
upvoted 0 times
...

Save Cancel