A hospital seeks a unified sign-in among several clinics to cut down on overhead from creating individual accounts. Which solution best satisfies this need while still transferring user attributes between locations?
Extend local user directories across all clinics with one password policy
Adopt a recognized single sign-on solution that shares user details across sites
Allow each clinic to manage credentials independently using broader privileges
Replicate all user accounts to each clinic through periodic synchronization
A standardized single sign-on approach enables users to authenticate once, with their attributes accepted across multiple systems. This eliminates extra accounts for each clinic. Extending local directories keeps a single password policy but will not unify different locations under one process. Replicating accounts introduces unnecessary delays and management headaches. Allowing widespread privileges is risky and lacks control.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is Single Sign-On (SSO), and how does it work?
Open an interactive chat with Bash
What are the benefits of SSO compared to replicating user accounts across locations?
Open an interactive chat with Bash
What are SAML and OAuth, and why are they important in SSO?
Open an interactive chat with Bash
CompTIA Cloud+ CV0-004
Security
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
IT & Cybersecurity Package Join Premium for Full Access