MENU
Universal Containers is setting up a Sales Analytics app to track the sales performance across all regions. The role hierarchy is well-structured with separate branches for various global regions.
Viewer access has been provided to the regional sales reps based on the following roles.
* Regional Sales - APAC
* Regional Sales - EMEA
* Regional Sales - LATAM
* Regional Sales - NA
The CRM Analytics project team receives a request to extend Editor
access to the app to 20 'Superusers' across all regions.
What is the optimal solution?
Suggested Answer: A
Get Premium ANC-301 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
37 comments · newest first
MA
Marya
11 months ago
Definitely not B, roles are too rigid for this situation.
TR
Trinidad
11 months ago
Wait, can you really just group them like that? Sounds too simple.
JE
Jerlene
12 months ago
Why not just create new roles? Seems like overkill.
TA
Tamie
12 months ago
I agree, option A seems the most efficient.
HA
Haydee
1 year ago
A public group is the easiest way to manage access!
KA
Kami
1 year ago
I’m leaning towards A too, but I wonder if there are any limitations with public groups that we might have overlooked in our studies.
ST
Stephanie
1 year ago
I think we had a similar question where sharing rules were involved. C might work, but I feel like it's not the most straightforward solution here.
NI
Nida
1 year ago
I'm not entirely sure, but I think creating new roles might complicate things. B feels like it could be overkill for just 20 users.
GA
Gail
1 year ago
I remember we discussed the importance of using public groups for managing access in our last practice session. It seems like A could be the right choice.
DA
Dalene
1 year ago
This seems like a good opportunity to use a public group. That way, we can easily add or remove users from the group as needed, without having to update individual roles or sharing rules.
GE
Georgeanna
1 year ago
I'm leaning towards option A - creating a new public group for the Superusers. That way, we can easily manage their access without having to create new roles or sharing rules, which could get more complex.
PA
Pa
1 year ago
Okay, let's see. We have 20 'Superusers' who need Editor access to the app, and the existing roles are based on regional sales teams. I think creating a new public group might be the cleanest solution here.
CA
Carlota
1 year ago
Hmm, I'm a bit unsure about this one. I'll need to carefully review the details around roles, groups, and sharing rules to determine the best approach.
AL
Alton
1 year ago
This looks like a pretty straightforward permissions management question. I'd start by thinking through the different options and considering the pros and cons of each.
VA
Vallie
1 year ago
Hmm, I'm a bit unsure about the details of class attributes and module names. I'll need to think this through carefully.
ME
Meaghan
2 years ago
I bet the person who suggested creating new roles is the same one who came up with the idea for 'Superusers'. What's next, a 'Mega-Superuser' role?
DE
Dean
2 years ago
I'm not sure why anyone would choose to create new roles just for 20 users. That seems like a lot of unnecessary work.
VI
Viola
2 years ago
A) It definitely makes more sense to go with the public group option.
JU
Justine
2 years ago
C) Yeah, creating a new public group would be the most efficient solution.
PE
Pearline
2 years ago
B) I agree, creating new roles for just 20 users seems like overkill.
ME
Meghan
2 years ago
A) Create a new public group with these users and assign it the Editor app access.
AI
Aileen
2 years ago
What if we need to add more Superusers in the future? Creating a sharing rule would be a more flexible solution, in my opinion.
MA
Ma
2 years ago
C) Create a new sharing rule for these users and assign it the Editor app access.
TA
Tarra
2 years ago
B) Create new roles for these users and assign them the Editor app access.
SH
Sheridan
2 years ago
A) Create a new public group with these users and assign it the Editor app access.
JE
Jennie
2 years ago
I disagree, I believe creating new roles for these users would provide better control and organization.
LA
Laura
2 years ago
Creating new roles for the Superusers seems like an overkill. The public group option makes more sense to me.
JA
Jacklyn
2 years ago
C) I think a new sharing rule might be too complicated for this scenario.
DI
Diego
2 years ago
A) It's definitely the simpler solution for managing access.
NG
Nguyet
2 years ago
B) I agree, creating new roles for just 20 users does seem like too much.
KR
Kristian
2 years ago
A) Create a new public group with these users and assign it the Editor app access.
YE
Yen
2 years ago
I agree with Johnetta, creating a new public group seems like the most efficient way to grant access.
JA
Jaime
2 years ago
I think the optimal solution is to create a new public group with these users and assign it the Editor app access. This way, the CRM Analytics project team can easily manage the access rights for these Superusers.
AB
Abel
2 years ago
A) It's important to keep it simple and easy to manage for the project team.
ED
Eden
2 years ago
B) I agree, creating new roles for these users might complicate the hierarchy.
AL
Alberta
2 years ago
A) Create a new public group with these users and assign it the Editor app access.
JO
Johnetta
2 years ago
I think option A is the best solution.