Exam SC-300 topic 3 question 9 discussion

As the app is not visible for the users, I think the correct answer might be No,No,No. For reference: https://docs.microsoft.com/en-us/azure/active-directory/manage-apps/add-application-portal-configure

Tested in tenant answer is NO, YES, YES 1) No : because Nesting is not supported 2)Yes : because approver user will automatically assigned as owner 3) Yes : because assigned user will always have app on myapplication.microsoft.com portal

NYY: Group 3 is a nested group (nested into Group 1) and therefore members of group 3 do not gain access from that nesting. They must be added directly to group 1 (as group1 has access) or as an individual user to the app. User1 will be owner due to previously having approver permissions (prior to the change to self service). As for user 4 having access under the launcher, user4 is a direct member of group1 and the for "Visable to user" is targeted to users who are not assigned access, but this setting does not place the app in the my apps launcher, only being a member of group1 (or being directly assigned) will a user have the app in their myapps launcher.

1. NO - Only direct members will have access. Approved users will be added to Group 1. 2. Yes - The approver will automatically become owner of the Group 1 after self service is configured. 3. NO - Visible to users is NO. So no one will be able to see the app.

1. No - Nested groups are not supported 2. Yes - This was a hard one, because I couldn't find any online reference about it. But Selvaraj Rajan provided an experience from a test environment (s. below) 3. No - As many others have referenced, "Visible to users" = No wins over Assignment. Read again: https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/application-properties#visible-to-users

1) No : because Nesting is not supported 2)Yes : because approver user will automatically assigned as owner 3) NO : because "not visible" option is toggled for assigned user

1) No : because Nesting is not supported 2)Yes : because approver user will automatically assigned as owner 3) NO : because "not visible" option is toggled for assigned user

NO YES NO

NYN last NO: because "visible to users" is toggled as No, with this even assigned users won't see the app. Check the matrix in the link below: https://learn.microsoft.com/en-us/training/modules/plan-design-integration-of-enterprise-apps-for-sso/7-configure-pre-integrated-gallery-saas-apps

Good question, N,Y,N

2. Yes When you create a self service and save it, you will see a warning like below. Performing this action will replace any existing owners of the Group "XXXX" with the approver(s) you've selected. Would you like to do this? Yes No

NNN 1/ Very clear 2/ User1 can be an owner of the App1, not the owner of Group 1 which is Admin in the picture --> NO 3/ It is invisible to assign users -> NO

N - Try adding a group to an app. There is a warning that only difect members will have access to the app. Nested groups are ignored Y - Try configuring self-service for any app - there is a message that any existing owners of the group will be replaced with the approver N - The wole point of this setting is to hide an app from users (as explained in info next to the setting). Some apps don't need to be visible, or require any interaction from users, to work.

My answers will be N,Y,Y 1. Group 1 is assigned to App1 2. Admin is the owner of Group1 3. User4 is a member of Group1 according to the Powershell screenshot

N, Y, N,

NYN I concur

No Yes No Reading the information provided agree with the n,y,n group.