Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.
A
Best answer
Implement federated SSO with the enterprise identity provider and automated provisioning for SaaS users.
This is the best answer because federation centralizes authentication, and automated provisioning improves lifecycle management. Users sign in once through the identity provider, reducing password fatigue and help desk resets. When accounts are created, modified, or removed centrally, access changes can reach supported applications much faster, which helps with offboarding and reduces orphaned access.
B
Distractor review
Create one shared account for each application and store the passwords in a vault.
Shared accounts make accountability worse and create a larger blast radius if credentials are exposed. A vault is useful for secrets management, but it does not solve individual identity, least privilege, or timely offboarding concerns.
C
Distractor review
Keep local accounts in every SaaS app and reset passwords whenever staff change roles.
This preserves the exact problem shown in the exhibit: scattered accounts and manual maintenance. It increases administrative burden and makes consistent offboarding harder, especially as the number of applications grows.
D
Distractor review
Put the SaaS apps behind a network firewall and use source IP filtering instead of identity.
IP filtering does not replace identity-based access control and does not solve password resets or account lifecycle issues. Remote users, changing networks, and mobile access make IP-based controls too brittle for this requirement.