MENU
Consider a process that is scheduled to run 3 times a day (9AM, 1PM, 6PM). For each run, the process needs to consume data from a different queue.
What is the best way to implement this functionality?
Suggested Answer: B
Get Premium UiPath-ASAPv1 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
In UiPath Unassisted Task Mining, the correct type of licensing to check for running analysis is whether the customer has Mining units allocated. Task Mining uses AI algorithms to analyze user interactions and identify automation opportunities. Mining units are a specific type of licensing metric used to quantify and allocate the resources required for the Task Mining analysis. These units are consumed based on the volume of data analyzed and the computational resources utilized during the process. Ensuring the availability of Mining units is essential for the successful execution of Task Mining projects.
UiPath Task Mining Guide: Introduction to Task Mining
UiPath Licensing Guide: Understanding Licensing
32 comments · newest first
ST
Stephaine
10 months ago
I agree with A, it's straightforward and easy to manage!
CA
Candra
11 months ago
D is interesting, but what if the config file gets lost?
PA
Paul
11 months ago
C seems like overkill, why publish it 3 times?
DA
Darci
11 months ago
I think B is better for keeping track of changes over time.
QU
Quentin
11 months ago
Option A sounds efficient for passing queue names directly.
CH
Cherelle
12 months ago
I feel like storing the queue name in a configuration file, as in option D, could make it easier to manage changes without redeploying the process.
SH
Shawnta
12 months ago
This question reminds me of a practice scenario where we had to publish processes multiple times. Option C might be a bit overkill, though.
LA
Laurena
12 months ago
I'm not entirely sure, but I think using an asset to store the queue name could lead to complications if the asset isn't updated correctly.
AJ
Aja
1 year ago
I remember discussing the use of arguments in triggers, so option A seems like a straightforward approach.
ME
Meghan
1 year ago
Option D, adding the queue name in a configuration file and storing it in a shared location, seems like a good way to keep the code clean and maintainable. That way, if the queue names change, I only have to update the config file instead of modifying the process code.
ER
Erick
1 year ago
For a process that runs 3 times a day, I would probably go with option C and publish the process 3 times in Orchestrator, specifying the corresponding queue in the code. That way, I don't have to worry about managing the queue name in an asset or configuration file.
MA
Mariko
1 year ago
I'm a bit confused on this one. Should I be creating an asset to store the queue name, or is it better to just pass it as an argument? I'm not sure which option is the "best way" to implement this.
RO
Rochell
1 year ago
This seems like a straightforward question. I think option A is the best approach - using the queue name as an argument for the process and setting its value when creating the triggers.
VE
Veronica
1 year ago
I heard the developers were debating whether to use the queue name as an argument or to just throw darts at the keyboard and hope for the best. Either way, it's sure to be a wild ride!
VA
Valda
1 year ago
C) Publish the process 3 times in Orchestrator, specifying the corresponding queue in code.
LA
Latosha
1 year ago
B) Create an asset which stores the queue name and update the asset value after each run.
YO
Youlanda
1 year ago
A) Use the queue name as an argument for the process and set its value when creating the triggers.
VI
Viola
1 year ago
Option D seems like a reasonable approach. Storing the queue name in a configuration file and sharing it? Sounds like a good way to keep things centralized and maintainable.
JA
Janey
1 year ago
Using a configuration file for the queue name definitely simplifies the process and ensures consistency across runs.
BU
Bulah
1 year ago
I agree, having a shared location for the queue name in a configuration file makes it easier to manage and update.
BA
Barbra
1 year ago
Option D seems like a reasonable approach. Storing the queue name in a configuration file and sharing it? Sounds like a good way to keep things centralized and maintainable.
EM
Emerson
1 year ago
Option C? Really? Publishing the process three times in Orchestrator just to specify the queue? That's a bit overkill, don't you think?
DO
Dominic
1 year ago
D) Add the queue name in a configuration file and store it in a shared location.
AL
Alita
1 year ago
B) Create an asset which stores the queue name and update the asset value after each run.
ZI
Zita
1 year ago
A) Use the queue name as an argument for the process and set its value when creating the triggers.
KI
Kirk
1 year ago
Hmm, I'm not sure about Option B. Maintaining an asset and updating it after each run seems like it could get messy. Let's keep things simple, shall we?
AL
Aleisha
1 year ago
D) Add the queue name in a configuration file and store it in a shared location.
MA
Marylou
1 year ago
A) Use the queue name as an argument for the process and set its value when creating the triggers.
FR
Fredric
2 years ago
Option A sounds like the simplest and most straightforward approach. I can just pass the queue name as an argument and set it when creating the triggers. Easy peasy!
AN
Angelo
2 years ago
I see your point, Lewis. But I think option C could also work well if we want to keep things organized in Orchestrator.
LE
Lewis
2 years ago
I disagree, I believe option D is more efficient because it centralizes the queue name.
KR
Krissy
2 years ago
I think option A is the best way to implement this functionality.