Discuss UiPath UiPath-ASAPv1 Exam Topic 2 Question 38

How can the following situation be efficiency addressed?

A user receives a daily input file containing several items, which must be processed using the ACME application.

However, the processing should occur three days after obtaining the input file, not on the day the input file is provided.

AAdd the items in Orchestrator Queue on the same day the input file was received and when getting one item from Orchestrator Queue check when it was added.

BUse Redis instead or Orchestrator Queue for this scenario.

CAdd the items in Orchestrator three days later after receiving the input file.

DAdd the items in Orchestrator Queue on the same day the input file was received and specify a postpone date for each item

Suggested Answer: D

According to the UiPath documentation, the postpone date is a property of the queue item that specifies the date and time when the item becomes available for processing1.This can be used to delay the execution of a queue item until a certain condition is met, such as a specific date or a dependency on another process2. By adding the items in Orchestrator Queue on the same day the input file was received and specifying a postpone date for each item, the user can ensure that the items will be processed using the ACME application only after three days, without having to check the date of each item or use a different queue system.

Queues and Transactions - UiPath Documentation Portal1

How to get postponed date of queue item - Orchestrator - UiPath Community Forum3

Get Premium UiPath-ASAPv1 Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

27 comments · newest first

Jamal 10 months ago

I disagree, A adds unnecessary complexity with checking dates.

Louis 10 months ago

Wait, can we really use Redis for this? Sounds risky.

Lilli 10 months ago

C is straightforward, but I wonder if it could cause delays later on.

Mollie 10 months ago

I think D is better, specifying a postpone date sounds more organized.

Ellsworth 11 months ago

Option C seems the simplest, just delay the processing.

Shonda 11 months ago

Using Redis instead of Orchestrator Queue, like in option B, could be faster, but I can't recall if it supports the same features we need for this delay.

Catina 11 months ago

I feel like option D might be the most efficient since it allows us to set a postpone date for each item, but I’m not entirely confident about the implementation details.

Hollis 11 months ago

I think option C sounds straightforward, but it seems like it could complicate things if we need to manage the timing manually.

Mira 12 months ago

I remember we discussed using Orchestrator Queue for similar scenarios, but I'm not sure if checking the date when processing is the best approach.

Zona 12 months ago

I'm leaning towards option D as well. It seems like the most efficient way to handle this scenario, where we need to delay the processing by three days. Adding the items to the queue and specifying the postpone date is a clean solution.

Janella 12 months ago

Option C seems like the simplest solution to me. Just add the items to the Orchestrator three days after receiving the input file. That way, we don't have to worry about postpone dates or checking when the items were added. Seems like the most straightforward approach.

Candida 1 year ago

Hmm, I'm a bit confused. I'm not sure if using the Orchestrator Queue is the best approach here. Maybe option B, using Redis, could be a better solution? I'll need to think this through a bit more.

Norah 1 year ago

This seems like a straightforward problem. I think option D is the way to go - adding the items to the Orchestrator Queue on the same day and specifying a postpone date for each item to delay the processing.

Domitila 1 year ago

I think option D is more reliable in ensuring the processing occurs three days later.

Jesus 1 year ago

Option C is interesting, but it feels like it might introduce unnecessary delays or potential issues. I think option D is the cleanest solution.

Rodrigo 1 year ago

↳ replying to Jesus

Option C is interesting, but it feels like it might introduce unnecessary delays or potential issues.

Tuyet 1 year ago

I prefer option A, it seems simpler to implement.

Jenelle 1 year ago

Haha, I bet the ACME application is just as efficient as their famous cartoon anvils! Option D is the way to go, though. No need to overcomplicate things.

Carmen 1 year ago

I agree with Junita, option D seems most efficient.

Argelia 1 year ago

I'm not sure about using Redis for this scenario. Orchestrator Queue seems like a more appropriate solution, especially with the postpone date feature in option D.

Barrett 1 year ago

↳ replying to Argelia

User 3: I agree, using Orchestrator Queue with a postpone date seems like the most efficient solution for this scenario.

Ozell 1 year ago

↳ replying to Argelia

User 2: That sounds like a good idea, it would ensure the processing occurs three days after receiving the input file.

Jacquline 1 year ago

↳ replying to Argelia

User 1: I think option D is the best choice, we can add items in Orchestrator Queue and specify a postpone date.

Lindsay 1 year ago

Option D seems like the most efficient solution. Adding the items to the Orchestrator Queue on the same day and specifying a postpone date for each item sounds like a straightforward way to handle the 3-day delay requirement.

Stephen 1 year ago

↳ replying to Lindsay

That's a good point. It would definitely help in ensuring that the processing occurs three days after receiving the input file.

Norah 1 year ago

↳ replying to Lindsay

Junita 1 year ago

I think option D is the best solution.

UiPath-ASAPv1 Exam - Topic 2 Question 38 Discussion