Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Adobe Exam AD0-E722 Topic 7 Question 40 Discussion

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

A custom cron job has been added to an Adobe Commerce system to collect data for several reports. Its crontab. xml configuration is as follows:

The job is data intensive and runs for between 20 and 30 minutes each night.

Within a few days of deployment, it is noticed that the sites sitemap. xml file has not been updated since the new job was added.

What should be done to fix this issue?

Show Suggested Answer Hide Answer
Suggested Answer: B

The issue here is that the gather_reporting_data job is running for a long time and blocking the sitemap_generate job from running. The solution is to create a new cron group for the reporting job and specify <use_separate_process>i</use_separate_process> so that the reporting job runs in a separate process and does not block the sitemap_generate job.Reference: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/architecture/starter-architecture.html?lang=en#cron-groups-and-processes


Contribute your Thoughts:

Lashunda
12 days ago
I'm with Wayne on this one. If the job is that resource-intensive, maybe it's time to rethink the whole architecture. Just sayin'.
upvoted 0 times
Graciela
22 hours ago
C) Break the data gathering job into a number of smaller jobs, so that each individual job runs for a maximum of 5 minutes
upvoted 0 times
...
Alease
2 days ago
B) Create a new cron group for the reporting job, specifying i
upvoted 0 times
...
Nell
5 days ago
A) Change the schedule of the siten.aP_generate cron job to 30 0 * * *so that it runs after the gather_reporting_data job has completed.
upvoted 0 times
...
...
Yasuko
15 days ago
I think breaking the data gathering job into smaller jobs could also be a good solution.
upvoted 0 times
...
Lajuana
21 days ago
I agree with Noel, that might help fix the issue with the sitemap.xml file not being updated.
upvoted 0 times
...
Goldie
28 days ago
Hmm, I'm not sure. Changing the schedule seems like a bandaid solution. I think option C is the best long-term fix.
upvoted 0 times
Ivory
15 days ago
I think both options C and B could work well together to solve the problem.
upvoted 0 times
...
Van
19 days ago
But wouldn't creating a new cron group also help with the issue?
upvoted 0 times
...
Eleonora
20 days ago
I agree, breaking the job into smaller parts seems like a good idea.
upvoted 0 times
...
...
Loreta
1 months ago
I like option B. Separating the reporting job into its own cron group sounds like a smart way to manage the process without interfering with other tasks.
upvoted 0 times
Janey
2 days ago
User 3: Definitely, that way it won't interfere with other tasks and the sitemap.xml file can be updated properly.
upvoted 0 times
...
Wenona
16 days ago
User 2: Agreed, separating the reporting job into its own cron group seems like the best solution.
upvoted 0 times
...
Geraldine
18 days ago
User 1: I think option B is a good idea. It will help keep things organized.
upvoted 0 times
...
...
Noel
1 months ago
I think we should change the schedule of the siten.aP_generate cron job.
upvoted 0 times
...
Skye
2 months ago
C is the way to go! Breaking up the job into smaller tasks will ensure the sitemap gets updated regularly without any delays.
upvoted 0 times
Ernie
17 days ago
I agree. Splitting the job into smaller tasks seems like the best solution for this issue.
upvoted 0 times
...
Eleonora
1 months ago
That's a good point. It will definitely help in keeping the sitemap up to date.
upvoted 0 times
...
Lorrie
1 months ago
C is the way to go! Breaking up the job into smaller tasks will ensure the sitemap gets updated regularly without any delays.
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