New Year Sale ! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Exam Platform App Builder Topic 9 Question 83 Discussion

Actual exam question for Salesforce's Platform App Builder exam
Question #: 83
Topic #: 9
[All Platform App Builder Questions]

An app builder at Cloud Kicks has been working on changes to a custom Shoe Sales app in a sandbox and is ready to deploy their changes to production with a change set. Part of the work included updates to a permission set.

What should the app builder take into consideration when deploying the change set to production?

Show Suggested Answer Hide Answer
Suggested Answer: C

The deployed permission set will merge with the existing permission set in production, meaning changes made in the sandbox will be added to the existing permission set after deployment. Reference:

Salesforce Help - Permission Sets


Contribute your Thoughts:

Mignon
6 months ago
I'm going with A. Wouldn't want any sneaky changes creeping into the production environment. These shoes need to stay on lock-down!
upvoted 0 times
Lauran
5 months ago
Definitely, we don't want any unexpected changes causing issues in production.
upvoted 0 times
...
Rikki
5 months ago
I agree, A seems like the safest option to ensure only the intended changes are deployed.
upvoted 0 times
...
...
Felice
6 months ago
As a wise man once said, 'With great power comes great responsibility.' Gotta be on top of those permission set changes, you know?
upvoted 0 times
Herminia
5 months ago
C) The deployed permission set will manage with the existing permission set.
upvoted 0 times
...
Maurine
5 months ago
A) The deployed permission set will only contain changes related to the change set.
upvoted 0 times
...
...
Lonna
6 months ago
Hmm, I'm not sure about this one. C sounds reasonable, but I'll double-check the documentation just to be safe.
upvoted 0 times
...
Vonda
6 months ago
I think B is the correct answer. Changes to field-level security won't be applied, so I need to be extra careful with that.
upvoted 0 times
Sage
5 months ago
I agree. It's better to be cautious and make sure everything is in order before deploying to production.
upvoted 0 times
...
Nakisha
6 months ago
That's a good point. It's important to double-check all the changes before deploying.
upvoted 0 times
...
Charlette
6 months ago
I think B is the correct answer. Changes to field-level security won't be applied, so I need to be extra careful with that.
upvoted 0 times
...
Tennie
6 months ago
Yes, it's important to double-check all the permissions to avoid any issues in production.
upvoted 0 times
...
Van
6 months ago
I agree, we need to make sure we manually update the field-level security after deploying the change set.
upvoted 0 times
...
...
Helaine
7 months ago
Option D seems logical, as the existing permission set will be completely overwritten. I don't want any surprises in production!
upvoted 0 times
Leonida
6 months ago
Definitely, we don't want any unexpected changes to the permission set.
upvoted 0 times
...
Tricia
6 months ago
B) Change to field-level security in the permission set will not be applied.
upvoted 0 times
...
Ahmad
6 months ago
I agree, option D is the safest choice to avoid any surprises in production.
upvoted 0 times
...
Sheron
6 months ago
A) The deployed permission set will only contain changes related to the change set.
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77