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-E722 Topic 5 Question 28 Discussion

Actual exam question for Adobe's AD0-E722 exam
Question #: 28
Topic #: 5
[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:

Lavelle
2 months ago
Option B seems like overkill - creating a whole new cron group just for one job? I'd go with Option C, it's the most elegant solution that directly addresses the root cause of the problem.
upvoted 0 times
...
Celeste
2 months ago
Haha, imagine if the dev team just set the reporting job to run at midnight, right after the sitemap job. That would be a classic case of 'the left hand not knowing what the right hand is doing'!
upvoted 0 times
Edward
1 months ago
A: Definitely, we need to make sure the jobs don't overlap like that.
upvoted 0 times
...
Rashad
1 months ago
C: Breaking the data gathering job into smaller jobs could also solve the issue.
upvoted 0 times
...
Ruth
2 months ago
B: Yeah, creating a new cron group for the reporting job might help too.
upvoted 0 times
...
Dianne
2 months ago
A: We should change the schedule of the siten.aP_generate cron job to run after the gather_reporting_data job.
upvoted 0 times
...
Eleonore
2 months ago
C: Breaking the data gathering job into smaller jobs could also help with the issue.
upvoted 0 times
...
Judy
2 months ago
B: Yeah, changing the schedule of the siten.aP_generate cron job makes sense to prevent overlap.
upvoted 0 times
...
Melissa
2 months ago
A: Option A sounds like the best solution to avoid conflicts between the jobs.
upvoted 0 times
...
...
Vinnie
3 months ago
The sitemap.xml issue is clearly due to the long-running reporting job. Option C looks like the best solution to me - breaking the job into smaller tasks that each finish within 5 minutes should prevent the sitemap from getting stale.
upvoted 0 times
Crissy
1 months ago
Creating a new cron group for the reporting job might be worth trying. It could help with the sitemap.xml problem.
upvoted 0 times
...
Virgilio
2 months ago
Changing the schedule of the siten.aP_generate cron job could also work. It would ensure it runs after the reporting job is done.
upvoted 0 times
...
Melodie
2 months ago
I agree, splitting the job into smaller tasks is a smart move. It should help keep the sitemap updated.
upvoted 0 times
...
Roxane
2 months ago
Option C sounds like a good idea. Breaking the job into smaller tasks could solve the issue.
upvoted 0 times
...
...
Herschel
3 months ago
I think breaking the data gathering job into smaller jobs could also help.
upvoted 0 times
...
Lura
3 months ago
I agree with Twana. Running it after the gather_reporting_data job makes sense.
upvoted 0 times
...
Twana
3 months ago
I think we should change the schedule of the siten.aP_generate cron job.
upvoted 0 times
...

Save Cancel