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-E716 Topic 7 Question 16 Discussion

Actual exam question for Adobe's AD0-E716 exam
Question #: 16
Topic #: 7
[All AD0-E716 Questions]

When attempting operations that require lengthy processing, a merchant on Adobe Commerce Cloud receives a timeout error after 180 seconds.

How would the developer deal with this issue?

Show Suggested Answer Hide Answer
Suggested Answer: B

The developer can deal with this issue by modifying the admin path timeout value in seconds in the Fastly Configuration section > Advanced Configuration in the Admin Panel. Fastly is a cloud-based caching service that improves site performance and security for Adobe Commerce Cloud projects. Fastly has a default timeout value of 180 seconds for admin requests, which means that any request that takes longer than 180 seconds will be terminated and result in a timeout error. The developer can increase this value to allow longer processing time for admin requests without causing errors. The developer also needs to save the configuration and upload VCL to Fastly to apply the changes. Verified Reference: [Magento 2.4 DevDocs]


Contribute your Thoughts:

Simona
5 months ago
I see your point. Option B does seem more efficient in resolving the timeout error quickly.
upvoted 0 times
...
Mari
5 months ago
That's a good point. Option B allows for immediate action without relying on external support.
upvoted 0 times
...
Carisa
5 months ago
But don't you think submitting a support ticket for the changes in option C would cause delays?
upvoted 0 times
...
Simona
6 months ago
I personally think option C is more reliable. Modifying the admin timeout in the config.php file makes sense to me.
upvoted 0 times
...
Mari
6 months ago
I agree with you, setting the Admin path timeout value in Fastly seems like the right solution.
upvoted 0 times
...
Carisa
6 months ago
I think the best approach would be option B.
upvoted 0 times
...
Jenelle
6 months ago
I personally think option C is the best choice, modifying the admin timeout in the app/etc/config.php file and submitting a support ticket for the changes.
upvoted 0 times
...
Gerald
7 months ago
I agree with Mari, but option B might also be a good solution by setting the Admin path timeout in Fastly Configuration.
upvoted 0 times
...
Mari
7 months ago
I think option A could work, modifying the admin timeout in the .magento.app.yaml file.
upvoted 0 times
...

Save Cancel