Pegasystems PEGACPSA23V1 Exam - Topic 2 Question 20 Discussion

Actual exam question for Pegasystems's PEGACPSA23V1 exam

Question #: 20
Topic #: 2

[All PEGACPSA23V1 Questions]

Which two use cases are supported by configuring a mobile channel in App Studio? (Choose Two)

AGrant access to the application for a specific user.

BSet the width of an application icon to 180x180 pixels.

CConfigure a left swipe behavior to open a message.

DLock the application after 20 minutes of inactivity.

Show Suggested Answer

Suggested Answer: C, D

An authority matrix in Pega is used to manage complex decision-making processes that depend on various levels of organizational authority:

C . Any overtime -> Manager of Supervisor. This condition involves hierarchical decision-making where approval authority escalates beyond the immediate supervisor, making it appropriate for an authority matrix to define and automate the approval paths based on the organizational structure.

D . Regular 40 hours -> Supervisor of Employee. Although this appears straightforward, using an authority matrix helps in organizations where different supervisors might have varying levels of authority based on departmental rules or other factors, thus standardizing the approval process across diverse units.

by Gerardo at Dec 10, 2024, 04:04 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Narcisa

6 months ago

A is a must, but I don't see why D is needed.

upvoted 0 times

...

Eve

6 months ago

Not sure about B, seems irrelevant to mobile channels.

upvoted 0 times

...

Nichelle

6 months ago

Wait, can you really configure swipe actions? That's cool!

upvoted 0 times

...

Justine

7 months ago

I think D is also important for security.

upvoted 0 times

...

Lettie

7 months ago

Definitely A and C! Those are key features.

upvoted 0 times

...

Daren

7 months ago

I don't recall anything about setting icon sizes, so I’m leaning towards C and D, but I could be wrong.

upvoted 0 times

...

Jamal

7 months ago

I feel like granting access to specific users was mentioned in our study materials, so maybe option A is one of the answers.

upvoted 0 times

...

Roosevelt

7 months ago

I'm not entirely sure, but I remember something about locking applications. Is that option D?

upvoted 0 times

...

Ammie

8 months ago

I think option C sounds familiar, like we practiced configuring swipe behaviors in our last session.

upvoted 0 times

...

Enola

8 months ago

This looks straightforward to me. Options A and D are clearly about user access and security, which are common mobile channel use cases. I'll select those two and move on.

upvoted 0 times

...

Lashanda

8 months ago

I'm a bit confused by this question. The options don't seem to directly match the question about mobile channel configuration. I'll need to re-read the question and options carefully to make sure I understand what they're asking.

upvoted 0 times

...

Ciara

8 months ago

Okay, let's see here. I think options C and D are more about mobile app features, while A and B seem more related to the mobile channel configuration. I'll go with those two.

upvoted 0 times

...

Brandon

8 months ago

Hmm, this seems like a tricky one. I'll need to carefully read through the options and think about which use cases are specifically related to configuring a mobile channel.

upvoted 0 times

...

Kristeen

1 year ago

Okay, time to put my mobile app expertise to the test. I'm going with C and D - swipe actions and inactivity locks are mobile staples.

upvoted 0 times

Hoa

11 months ago

Looks like we both made the right choices for configuring a mobile channel in App Studio.

upvoted 0 times

...

Winfred

12 months ago

Definitely, inactivity locks are important for security on mobile devices.

upvoted 0 times

...

Lajuana

1 year ago

I agree, swipe actions are so convenient for mobile users.

upvoted 0 times

...

Olive

1 year ago

Ha, no way A is right. Granting user access is more of a security feature, not a mobile-specific use case. I'll pick C and D.

upvoted 0 times

Nathan

11 months ago

C and D make sense for mobile use cases, they involve specific mobile behaviors.

upvoted 0 times

...

Kristeen

12 months ago

I think C and D are the correct options for configuring a mobile channel.

upvoted 0 times

...

Lai

1 year ago

I agree, A is definitely not a mobile-specific use case.

upvoted 0 times

...

Cherelle

1 year ago

Hmm, this is a tricky one. I'm thinking C and D are the way to go. Locking the app and swipe navigation are classic mobile use cases.

upvoted 0 times

...

Arlette

1 year ago

I'm going to go with B and C. The mobile icon size and swipe actions are clearly mobile-related features.

upvoted 0 times

Gertude

12 months ago

It's important to focus on mobile-related features when configuring a mobile channel.

upvoted 0 times

...

Brett

1 year ago

Definitely, those options are specific to mobile channels in App Studio.

upvoted 0 times

...

Kathrine

1 year ago

Setting the width of an application icon and configuring swipe behavior are key mobile features.

upvoted 0 times

...

Albina

1 year ago

I agree, B and C are the correct options for configuring a mobile channel.

upvoted 0 times

...

Elise

1 year ago

I believe D could also be a valid use case. Locking the application after inactivity can enhance security.

upvoted 0 times

...

Magdalene

1 year ago

C and D seem like the correct answers here. Configuring swipe behavior and locking the app after inactivity are definitely mobile-focused use cases.

upvoted 0 times

Tiera

1 year ago

I agree, configuring swipe behavior and locking the app after inactivity are important for mobile channels.

upvoted 0 times

...

Tess

1 year ago

C and D are the correct answers. They are mobile-focused use cases.

upvoted 0 times

...

Rashida

1 year ago

I agree with Owen. Granting access and configuring swipe behavior are important for mobile channels.

upvoted 0 times

...

Owen

1 year ago

I think A and C are the supported use cases.

upvoted 0 times

...