Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Pegasystems Exam PEGACPSA23V1 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)

Show Suggested Answer Hide 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.


Contribute your Thoughts:

Kristeen
2 months 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
Winfred
9 days ago
Definitely, inactivity locks are important for security on mobile devices.
upvoted 0 times
...
Lajuana
1 months ago
I agree, swipe actions are so convenient for mobile users.
upvoted 0 times
...
...
Olive
2 months 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
5 days ago
C and D make sense for mobile use cases, they involve specific mobile behaviors.
upvoted 0 times
...
Kristeen
17 days ago
I think C and D are the correct options for configuring a mobile channel.
upvoted 0 times
...
Lai
1 months ago
I agree, A is definitely not a mobile-specific use case.
upvoted 0 times
...
...
Cherelle
2 months 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
2 months 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
9 days ago
It's important to focus on mobile-related features when configuring a mobile channel.
upvoted 0 times
...
Brett
23 days ago
Definitely, those options are specific to mobile channels in App Studio.
upvoted 0 times
...
Kathrine
1 months ago
Setting the width of an application icon and configuring swipe behavior are key mobile features.
upvoted 0 times
...
Albina
1 months ago
I agree, B and C are the correct options for configuring a mobile channel.
upvoted 0 times
...
...
Elise
2 months ago
I believe D could also be a valid use case. Locking the application after inactivity can enhance security.
upvoted 0 times
...
Magdalene
2 months 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 months ago
I agree, configuring swipe behavior and locking the app after inactivity are important for mobile channels.
upvoted 0 times
...
Tess
1 months ago
C and D are the correct answers. They are mobile-focused use cases.
upvoted 0 times
...
...
Rashida
2 months ago
I agree with Owen. Granting access and configuring swipe behavior are important for mobile channels.
upvoted 0 times
...
Owen
2 months ago
I think A and C are the supported use cases.
upvoted 0 times
...

Save Cancel