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-E717 Topic 9 Question 26 Discussion

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

Which two recommended practices would a developer use on an Adobe Commerce Cloud Enhanced Integration Environment to get the best performance? (Choose two.)

Show Suggested Answer Hide Answer
Suggested Answer: A, D

On an Adobe Commerce Cloud Enhanced Integration Environment, enabling Fastly CDN (Content Delivery Network) can significantly improve performance by caching content closer to the user's location, reducing load times. Additionally, removing all of the integration's inactive branches helps to optimize the environment by decluttering and focusing resources on active development. Restricting catalog size may not be feasible or desirable, and disabling cron jobs can disrupt necessary background operations unless specifically needed for performance testing or troubleshooting.


Contribute your Thoughts:

Carli
4 months ago
Hmm, I'd go with A and B. Gotta keep that catalog lean and mean, and Fastly is a must-have for any serious e-commerce setup. Anything else is just asking for a performance nightmare.
upvoted 0 times
...
Jettie
4 months ago
A and C. Why run cron manually? That's just asking for headaches. Let's automate that sucker and enjoy the speed boost from Fastly!
upvoted 0 times
Adelaide
3 months ago
Yeah, running cron manually sounds like a hassle. Fastly CDN should give us a nice speed boost.
upvoted 0 times
...
Ernestine
4 months ago
I agree, automating cron is definitely the way to go. And enabling Fastly CDN will help with performance too.
upvoted 0 times
...
...
Tiara
4 months ago
D and B. Gotta keep those inactive branches out of the way, and optimize that catalog size. Efficiency is key!
upvoted 0 times
Georgene
3 months ago
D) Remove all of the integration's inactive branches.
upvoted 0 times
...
Carol
3 months ago
C) Disable cron and manually run as needed
upvoted 0 times
...
Yan
3 months ago
B) Restrict catalog size
upvoted 0 times
...
Francesco
4 months ago
A) Enable fastly CDN
upvoted 0 times
...
...
Isidra
5 months ago
I believe restricting catalog size could also help in improving performance by reducing data load.
upvoted 0 times
...
Jerrod
5 months ago
I would also go with removing inactive branches to optimize the integration.
upvoted 0 times
...
Janey
5 months ago
I agree with Huey. Fastly CDN can improve loading times for sure.
upvoted 0 times
...
Dean
5 months ago
A and B for sure. Can't have a huge catalog and no CDN, that's just asking for trouble!
upvoted 0 times
Lindsey
4 months ago
Removing inactive branches from the integration is a good practice as well.
upvoted 0 times
...
Pa
4 months ago
Disabling cron and manually running it as needed can also be beneficial.
upvoted 0 times
...
Helga
4 months ago
Definitely, restricting catalog size can also help improve performance.
upvoted 0 times
...
Olene
5 months ago
I agree, having a fastly CDN is crucial for performance.
upvoted 0 times
...
...
Huey
5 months ago
I think enabling fastly CDN would definitely help with performance.
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