DRAG DROP A company has the following custom permission set: 
Change Assignable to true, publish the app, then add Permission Sets page permission. You need Assignable set before anything else or it won't show up, and publishing registers it in the environment. The last step (adding page permission) is needed so users can actually access/manage the set. ObsoleteState and IncludedPermissionSets are common distractors here, so don't get tripped up! Pretty sure this is what Microsoft expects but let me know if anyone sees it differently.


You need to provide the following implementation for a third permission set: • Create a new Permission Set C that is a composite of Permission Set A and Permission Set B. • Assign Permission Set C to a user. You need to ensure that the user has only read access to the Job table. Solution: Set the Excluded Permission Sets property to Permission Set B. Does the solution meet the goal?



