Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Adobe Exam AD0-E706 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:

Jaleesa
2 months 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
2 months 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
2 months 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 months ago
D) Add a patch for extension so it uses the subdirectory var/internal/ instead
upvoted 0 times
...
Melissia
2 months ago
C) Request the vendor make the directory configurable in the Magento admin
upvoted 0 times
...
Lashaun
2 months ago
B) Declare a shared mount for the internal/directory in .magento. app.yaml
upvoted 0 times
...
Carylon
2 months ago
A) Create a symlink from /top/internal to the internal/ folder
upvoted 0 times
...
...
Lacey
2 months 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
2 months ago
D) Add a patch for extension so it uses the subdirectory var/internal/ instead
upvoted 0 times
...
Shalon
2 months ago
B) Declare a shared mount for the internal/directory in .magento. app.yaml
upvoted 0 times
...
Harley
2 months ago
A) Create a symlink from /top/internal to the internal/ folder
upvoted 0 times
...
...
Harrison
3 months ago
I agree with Kenneth, option B sounds like the best solution to ensure compatibility with Magento Commerce Cloud
upvoted 0 times
...
Chauncey
3 months 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
2 months ago
D) Adding a patch for the extension to use the subdirectory var/internal/ is another possible fix
upvoted 0 times
...
Layla
2 months ago
C) Requesting the vendor to make the directory configurable in the Magento admin might be a good solution
upvoted 0 times
...
Mira
2 months ago
A) Creating a symlink from /top/internal to the internal/ folder could work too
upvoted 0 times
...
Louann
2 months ago
B) Declaring a shared mount for the internal/ directory in .magento.app.yaml is the best option
upvoted 0 times
...
...
Kenneth
3 months 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
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77