Deal of The Day! 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

Google Cloud Digital Leader Exam - Topic 15 Question 53 Discussion

Your company has a requirement to run manual tests on their web products for UX research before it is released to end customers. The people who will do the tests are external to the company. They will either use their own Gmail id or be given temporary email ids using the applications and record-ing their inputs in another app. The UX testing is done in the last week of the month. Each month the UX testers could be different. How should the IT team manage the users?
A) Since the app is anyways going to be public, create permanent credentials for the UX testers that they can conveniently use each time.
B) It would be a security issue to have users come and go. Recommend that the test-ers be permanently hired to plug the vulnerability issue.
C) It would be a security issue to have users come and go. Recommend that the test-ers be permanently hired to plug the vulnerability issue.
D) Create a Group with the permissions required to do the test and record their in-puts. When users arrive each week, add them to the group and after the testing period, remove them from the group.

Google Cloud Digital Leader Exam - Topic 15 Question 53 Discussion

Actual exam question for Google's Cloud Digital Leader exam
Question #: 53
Topic #: 15
[All Cloud Digital Leader Questions]

Your company has a requirement to run manual tests on their web products for UX research before it is released to end customers. The people who will do the tests are external to the company. They will either use their own Gmail id or be given temporary email ids using the applications and record-ing their inputs in another app. The UX testing is done in the last week of the month. Each month the UX testers could be different. How should the IT team manage the users?

Show Suggested Answer Hide Answer
Suggested Answer: A

by Jacki at May 17, 2024, 10:00 PM

Limited Time Offer

25%

Off

Get Premium Cloud Digital Leader Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Anglea
7 months ago
Temporary email ids are a good idea for security, but what about usability?
upvoted 0 times
...
Maile
8 months ago
Wait, can we really trust external testers with sensitive data?
upvoted 0 times
...
Bernadine
8 months ago
Hiring testers permanently? That seems excessive.
upvoted 0 times
...
Julianna
8 months ago
I agree, creating a group is the best way to manage access!
upvoted 0 times
...
Antonio
8 months ago
Permanent credentials sound convenient but risky.
upvoted 0 times
...
Nancey
9 months ago
I recall that security is a big concern in these scenarios. I think option D makes sense, but I wonder if there are any risks with adding users to a group temporarily.
upvoted 0 times
...
Darrin
9 months ago
I feel like having testers permanently hired might be overkill. I lean towards option D, but I’m not completely confident about the logistics of adding and removing users each week.
upvoted 0 times
...
Alease
9 months ago
I think we practiced a similar question about temporary access for external users. Option D sounds familiar, but I’m a bit uncertain about how to manage the group permissions effectively.
upvoted 0 times
...
Maybelle
9 months ago
I remember discussing the importance of managing user access for security reasons, but I'm not sure if creating permanent credentials is the best approach.
upvoted 0 times
...
Desiree
9 months ago
The group approach sounds promising. That way I can easily add and remove users as needed without compromising security. I'll explore that option further.
upvoted 0 times
...
Cherry
9 months ago
Permanently hiring the testers seems like overkill. There has to be a more efficient way to handle the temporary access needs.
upvoted 0 times
...
Ira
9 months ago
Creating permanent credentials could be convenient, but it's a security risk if the testers come and go. I'll have to weigh that against the hassle of managing temporary accounts.
upvoted 0 times
...
Colette
9 months ago
This seems like a tricky security issue. I'll need to think carefully about the pros and cons of each approach.
upvoted 0 times
...
Javier
9 months ago
Alright, I think I've got this. The valid SRV records are _collab-edge._tls.example.com and _sips_tcp.example.com. I'm confident those are the correct answers.
upvoted 0 times
...
Sunny
9 months ago
Hmm, I'm a bit unsure about this one. I know back-to-back order processing is when the seller doesn't have the product and has to get it from somewhere else, but I'm not sure I fully understand all the different scenarios where that would apply.
upvoted 0 times
...
Marsha
9 months ago
This is a straightforward question about BFD operating modes. The key is to remember that in the active mode, the local end is the one sending the BFD Control packets at regular intervals. So the answer here is "active".
upvoted 0 times
...
Dana
10 months ago
I'm leaning towards the 1:n relationship since I recall it being common for parent-child associations.
upvoted 0 times
...
Launa
1 year ago
I'm with Joaquin and Brock on this one. Option D is the way to go. Gotta love those IT security measures that don't make life a living hell for everyone involved.
upvoted 0 times
...
Thomasena
1 year ago
Haha, permanently hiring the testers? That's overkill. Why not just have them come and go as needed? It's not like they're going to steal the company secrets or something.
upvoted 0 times
Denae
1 year ago
B) It would be a security issue to have users come and go. Recommend that the testers be permanently hired to plug the vulnerability issue.
upvoted 0 times
...
Lanie
1 year ago
D) Create a Group with the permissions required to do the test and record their inputs. When users arrive each week, add them to the group and after the testing period, remove them from the group.
upvoted 0 times
...
Sunshine
1 year ago
A) Since the app is anyways going to be public, create permanent credentials for the UX testers that they can conveniently use each time.
upvoted 0 times
...
...
Brock
1 year ago
I agree, creating a dedicated group for the external testers and managing their access that way is a good approach. Keeps things secure and organized.
upvoted 0 times
Wenona
1 year ago
A) Since the app is anyways going to be public, create permanent credentials for the UX testers that they can conveniently use each time.
upvoted 0 times
...
Dulce
1 year ago
D) Create a Group with the permissions required to do the test and record their inputs. When users arrive each week, add them to the group and after the testing period, remove them from the group.
upvoted 0 times
...
Freida
1 year ago
A) Since the app is anyways going to be public, create permanent credentials for the UX testers that they can conveniently use each time.
upvoted 0 times
...
...
Joaquin
1 year ago
Option D seems like the most practical solution. Temporary user accounts with the required permissions make more sense than permanent credentials.
upvoted 0 times
Kelvin
1 year ago
Yes, it's important to control access to sensitive information. Creating temporary accounts for the UX testers during the testing period is a smart approach.
upvoted 0 times
...
Phyliss
1 year ago
I agree, it would be a security risk to have users with permanent access. Adding and removing them from a group is a good way to manage access.
upvoted 0 times
...
Elfriede
1 year ago
Option D seems like the most practical solution. Temporary user accounts with the required permissions make more sense than permanent credentials.
upvoted 0 times
...
...
Lizbeth
1 year ago
I disagree. I think option A is more convenient for the testers and would make the process smoother.
upvoted 0 times
...
Val
1 year ago
I agree with Nan. Having temporary access for the UX testers is the most secure option.
upvoted 0 times
...
Nan
1 year ago
I think option D is the best way to manage the users. It ensures security by only giving temporary access.
upvoted 0 times
...

Save Cancel