BlackFriday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Pegasystems Exam PEGAPCRSA80V1_2019 Topic 7 Question 66 Discussion

Actual exam question for Pegasystems's PEGAPCRSA80V1_2019 exam
Question #: 66
Topic #: 7
[All PEGAPCRSA80V1_2019 Questions]

You are assigned to develop a set of activities using a popular HR application. The application loads after you start interrogation from Pega Robot Studio, but you notice that you are unable to use the Robot Studio Interrogator to drag and drop over the desired controls.

Why are you unable to interrogate the desired application controls?

Show Suggested Answer Hide Answer
Suggested Answer: D

by Cecilia at Jun 19, 2024, 04:19 AM

Limited Time Offer

25%

Off

Get Premium PEGAPCRSA80V1_2019 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Jerrod
4 months ago
Haha, I'm imagining the developer trying to interrogate the application like a spy interrogating a suspect. 'Where are the controls?! Tell me everything!'
upvoted 0 times
...
Aleisha
4 months ago
I'm leaning towards option B. The StartMethod is set to MonitorAll, but the path property is undefined. That's probably why the interrogation is failing.
upvoted 0 times
Graciela
3 months ago
I'm not sure, but I think it could be option C. The StartMethod is set to Start, but the TargetPath property is undefined.
upvoted 0 times
...
Cyril
3 months ago
I agree with you, it could be option A. The StartMethod being set to StartAndWait might be causing the issue.
upvoted 0 times
...
Billy
3 months ago
I think it might be option A. The StartMethod is set to StartAndWait, but the TargetPath property is undefined.
upvoted 0 times
...
Gaston
3 months ago
Let's try setting the StartMethod to StartAndWait and see if that resolves the issue.
upvoted 0 times
...
King
3 months ago
Maybe we should double-check the path property and make sure it is properly defined.
upvoted 0 times
...
Herminia
3 months ago
I think you're right. Option B seems to be the most likely reason for the interrogation failure.
upvoted 0 times
...
...
Shawn
4 months ago
Aha! I bet the adapter's StartOnProject property is set to false. That's gotta be the issue here.
upvoted 0 times
Sue
4 months ago
B) The StartMethod on the adapter is set to MonitorAll, but the path property is undefined.
upvoted 0 times
...
Corinne
4 months ago
A) The StartMethod on the adapter is set to StartAndWait, but the TargetPath property is undefined.
upvoted 0 times
...
...
Lynsey
4 months ago
I think the problem might be with the adapter's StartOnProject property being set to false. That could be preventing us from interrogating the controls properly.
upvoted 0 times
...
Adelle
4 months ago
I'm not sure, but I think it could also be because the StartMethod is set to MonitorAll instead of Start. That might be causing the issue.
upvoted 0 times
...
Romana
4 months ago
I agree with Dion, that seems like the most likely reason. We need to define the TargetPath for the controls to be interrogated.
upvoted 0 times
...
Dion
5 months ago
I think the reason we can't interrogate the controls is because the StartMethod is set to StartAndWait, but the TargetPath is undefined.
upvoted 0 times
...
Jina
5 months ago
Hmm, I think the answer is C. The StartMethod is set to Start, but the TargetPath property is undefined, so it can't find the application controls to interrogate.
upvoted 0 times
Annelle
4 months ago
C) The StartMethod on the adapter is set to Start, but the TargetPath property is undefined.
upvoted 0 times
...
Delbert
4 months ago
B) The StartMethod on the adapter is set to MonitorAll, but the path property is undefined.
upvoted 0 times
...
Sang
4 months ago
A) The StartMethod on the adapter is set to StartAndWait, but the TargetPath property is undefined.
upvoted 0 times
...
...

Save Cancel