Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

UiPath-ARDv1 Exam - Topic 3 Question 104 Discussion

Actual exam question for UiPath's UiPath-ARDv1 exam
Question #: 104
Topic #: 3
[All UiPath-ARDv1 Questions]

A developer created an automation project in the Robotic Enterprise (RE) Framework which needs to log into a website using different credentials depending on the account and machine it runs on. If the value is not defined for the account and machine, the developer needs the process to throw an error. For security reasons, the credentials for the login are stored in Orchestrator as Credential Assets with the Value Per Account-Machine option.

Which steps should the developer perform to use the Orchestrator asset in the project?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

0/2000 characters
Laurene
6 months ago
Are we sure about the Assets vs. Settings debate? Seems confusing!
upvoted 0 times
...
Lashandra
6 months ago
Definitely A, I've done this before and it works perfectly.
upvoted 0 times
...
Cristal
6 months ago
Wait, why would you enable the Global Value? That seems risky!
upvoted 0 times
...
Izetta
7 months ago
I think B makes more sense, Settings sheet is the way to go.
upvoted 0 times
...
Lyndia
7 months ago
Option A is correct! You need the Global Value disabled.
upvoted 0 times
...
Rosann
7 months ago
I vaguely recall that the Orchestrator asset needs to be referenced correctly, but I can't remember if it should be in the Assets or Settings sheet. I hope I chose the right one!
upvoted 0 times
...
Elenora
7 months ago
I'm a bit confused about whether to use the Global Value option. I thought it was only for shared credentials, but this scenario seems different.
upvoted 0 times
...
William
7 months ago
I think we practiced a similar question where we had to decide between the Assets and Settings sheets in Config.xlsx. I feel like the Assets sheet is the right choice here.
upvoted 0 times
...
Carmen
8 months ago
I remember we discussed the importance of the Global Value setting for Credential assets, but I'm not sure if it should be enabled or disabled in this case.
upvoted 0 times
...
Julianna
8 months ago
I think I've got it. The key is to create the Credential asset with the Global Value disabled, and then add the asset name to the Settings sheet in Config.xlsx. That way, the project can use the account-specific credentials stored in Orchestrator.
upvoted 0 times
...
Jesusita
8 months ago
Hmm, I'm not sure about the difference between the Assets and Settings sheets in Config.xlsx. I'll need to review the RE Framework documentation to make sure I'm handling this correctly.
upvoted 0 times
...
Nguyet
8 months ago
Okay, I've got this. The question says the credentials are stored in Orchestrator as Credential Assets with the Value Per Account-Machine option. So I'll need to create the asset with the Global Value disabled, and then add the asset name to the Settings sheet in Config.xlsx.
upvoted 0 times
...
Dacia
8 months ago
I'm a little confused about the Global Value setting. Should it be disabled or enabled? I'll need to double-check the details in the question.
upvoted 0 times
...
Gene
8 months ago
Hmm, this seems straightforward. I think the key is to create a Credential asset in Orchestrator with the Value Per Account-Machine option, and then reference that asset in the project.
upvoted 0 times
...
Latrice
1 year ago
Okay, let's see... Credential asset, Config.xlsx, and throwing errors. Sounds like a regular day in the life of a developer. I've got this!
upvoted 0 times
Alpha
12 months ago
D) Create a Credential asset with the Global Value enabled.
upvoted 0 times
...
Marleen
1 year ago
C) Create a Credential asset with the Global Value enabled.
upvoted 0 times
...
Francis
1 year ago
B) Create a Credential asset with the Global Value disabled.
upvoted 0 times
...
Kaycee
1 year ago
A) Create a Credential asset with the Global Value disabled.
upvoted 0 times
...
...
Marsha
1 year ago
Wait, did someone say 'Robotic Enterprise Framework'? Sounds like they're building a robot army to take over the world! *cue evil laughter*
upvoted 0 times
...
Fernanda
1 year ago
Hmm, I think I'll go with option B. Keeping those credentials secure is key, you know? Gotta love that Value Per Account-Machine feature.
upvoted 0 times
Edward
1 year ago
User 2: Absolutely, can't be too careful with sensitive information like login credentials.
upvoted 0 times
...
Edwin
1 year ago
User 1: I agree, option B is the way to go. Security is always a top priority.
upvoted 0 times
...
...
Rashida
1 year ago
I believe option B is the correct one. Creating a Credential asset with the Global Value disabled and adding a row in the Settings sheet in Config.xlsx seems like the right approach.
upvoted 0 times
...
Minna
1 year ago
Ah, so it's all about those pesky Orchestrator assets! I better read this carefully or I'll end up throwing the wrong kind of error.
upvoted 0 times
Belen
12 months ago
Option A) Definitely, we don't want any mishaps with the credentials.
upvoted 0 times
...
Edison
12 months ago
Option A) That's correct, it's important to set it up properly to avoid errors.
upvoted 0 times
...
Kayleigh
1 year ago
Option A) Add a row in the Assets sheet in Config.xlsx with the name of the Orchestrator asset.
upvoted 0 times
...
Tamekia
1 year ago
Option A) Create a Credential asset with the Global Value disabled.
upvoted 0 times
...
...
Sharita
1 year ago
I agree with Valentin. Adding a row in the Assets sheet in Config.xlsx with the name of the Orchestrator asset makes sense.
upvoted 0 times
...
Valentin
1 year ago
I think the developer should create a Credential asset with the Global Value disabled.
upvoted 0 times
...

Save Cancel