Pegasystems PEGAPCRSA80V1_2019 Exam - Topic 5 Question 53 Discussion

Actual exam question for Pegasystems's PEGAPCRSA80V1_2019 exam

Question #: 53
Topic #: 5

[All PEGAPCRSA80V1_2019 Questions]

You are automating the login process for a web application. There are three possible scenarios that may occur: (1) You may successfully login, (2) you may not be successful logging in, or (3) you may log in but go to the change password screen.

Which control from the Toolbox do you use to determine which page you were on after performing the login function?

AWaitAll

BSwitch

CWaitAny

DSignal

Show Suggested Answer

Suggested Answer: A, D

by Audry at Nov 25, 2023, 04:13 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Billy

3 months ago

WaitAny? Really? That doesn't sound right!

upvoted 0 times

...

Nada

3 months ago

I thought WaitAny would be better for handling multiple outcomes.

upvoted 0 times

...

Tiera

3 months ago

WaitAll seems like it could work too, but not sure.

upvoted 0 times

...

Tamekia

4 months ago

Totally agree, Switch is the way to go!

upvoted 0 times

...

Carmen

4 months ago

I think you need to use the Switch control for this.

upvoted 0 times

...

Kiley

4 months ago

Signal seems like it’s more for notifying other processes, so I don't think that's the right choice for determining the login outcome.

upvoted 0 times

...

Lavelle

4 months ago

I'm a bit confused about whether to use WaitAll or Switch. I thought Switch was for branching logic, but maybe WaitAll could work too?

upvoted 0 times

...

Bambi

4 months ago

I remember practicing a similar question, and I feel like WaitAny could be relevant here since it waits for any of the scenarios to complete.

upvoted 0 times

...

Phyliss

5 months ago

I think we might need to use the Switch control to handle the different outcomes after logging in, but I'm not entirely sure.

upvoted 0 times

...

Dino

5 months ago

I'm a bit confused by the wording of this question. I'll need to re-read it a few times to make sure I understand the requirements before answering.

upvoted 0 times

...

Veronique

5 months ago

I'm confident the Switch control is the way to go here. It'll allow me to easily branch my logic based on the different login scenarios.

upvoted 0 times

...

Jaclyn

5 months ago

The WaitAny control sounds like it could work for this, since we need to handle multiple possible outcomes from the login process.

upvoted 0 times

...

Gerardo

5 months ago

Hmm, I'm a little unsure about this one. I'll have to think it through carefully to make sure I pick the right control.

upvoted 0 times

...

Carli

5 months ago

This seems like a pretty straightforward question. I think I'll go with the Switch control to handle the different login scenarios.

upvoted 0 times

...

Kristin

5 months ago

Hmm, I'm a bit unsure about this one. The graph doesn't seem to match any of the code options exactly. I'll need to think through the different graph types and syntax to try to figure out the right answer.

upvoted 0 times

...

Frankie

5 months ago

Option A sounds like a solid plan to me. Developing the baseline and target architectures for each plant, then doing a gap analysis, seems like the most comprehensive way to tackle this. It'll give us a clear roadmap for the transformation.

upvoted 0 times

...

Kimberlie

5 months ago

Hmm, I'm a bit unsure about this. Updating the pipeline in-flight seems risky, but I'm not sure if stopping and restarting is the best approach either.

upvoted 0 times

...

Chery

9 months ago

I'm feeling 'Switch' on this one. It's like a choose-your-own-adventure game, but for web automation. Buckle up, folks, it's time to navigate the login labyrinth!

upvoted 0 times

...

Ruthann

9 months ago

Aha! 'Switch' is the way to go. It's like a bouncer at a club - it checks who's coming in and sends them to the right place. Gotta love those control flow options!

upvoted 0 times

...

Lai

9 months ago

I'm going with 'Switch'. It's like having a choose-your-own-adventure book for your web app. Depending on where the login takes you, you can take the appropriate action.

upvoted 0 times

Kallie

8 months ago

Yeah, 'Switch' seems like the most logical choice for determining the next step after logging in.

upvoted 0 times

...

Maryrose

8 months ago

I would go with 'Switch' as well. It's like having different paths to follow after logging in.

upvoted 0 times

...

Ernest

8 months ago

I agree, 'Switch' is perfect for handling multiple scenarios after logging in.

upvoted 0 times

...

Quentin

9 months ago

I think 'Switch' is the right choice. It allows you to make decisions based on different outcomes.

upvoted 0 times

...

Taryn

10 months ago

Wow, this is a tricky one. I was initially leaning towards 'WaitAny', but after thinking it through, 'Switch' does seem like the more appropriate option. It's like choosing between a screwdriver and a hammer - sometimes you just need the right tool for the job.

upvoted 0 times

Alyce

8 months ago

Exactly, it helps in branching out based on the outcome of the login process. It's a versatile control.

upvoted 0 times

...

Reuben

8 months ago

I think 'Switch' makes sense too. It's like a decision-making tool to handle different scenarios.

upvoted 0 times

...

Alyce

9 months ago

I agree, 'Switch' would be the best option to determine which page you were on after logging in.

upvoted 0 times

...

Doretha

10 months ago

Hmm, I think the 'Switch' control would be the best choice here. It allows you to handle different scenarios based on the login outcome, which is exactly what the question is asking for.

upvoted 0 times