0
0
HLDsystem_design~5 mins

Authentication vs authorization in HLD - Quick Revision & Key Differences

Choose your learning style9 modes available
Recall & Review
beginner
What is authentication in system design?
Authentication is the process of verifying who a user is. It checks the user's identity, usually by asking for credentials like username and password.
Click to reveal answer
beginner
What does authorization mean in system design?
Authorization is the process of checking what a user is allowed to do. It controls access to resources based on user permissions.
Click to reveal answer
beginner
How are authentication and authorization different?
Authentication answers "Who are you?" while authorization answers "What can you do?" Authentication happens before authorization.
Click to reveal answer
beginner
Give a real-life example of authentication and authorization.
Logging into your email is authentication (proving who you are). Being able to read emails but not change account settings is authorization (what you can do).
Click to reveal answer
intermediate
Why is it important to separate authentication and authorization?
Separating them helps keep systems secure and organized. Authentication confirms identity once, then authorization controls access many times based on that identity.
Click to reveal answer
Which process verifies a user's identity?
AAuthentication
BAuthorization
CEncryption
DData validation
What does authorization control?
APassword strength
BUser identity
CUser permissions
DNetwork speed
Which happens first in a secure system?
AAuthorization
BAuthentication
CData backup
DLogging out
If a user can log in but cannot access admin pages, what is this an example of?
AAuthentication failure
BData corruption
CNetwork error
DAuthorization restriction
Which of these is NOT part of authentication?
ARole assignment
BFingerprint scan
CPassword check
DTwo-factor verification
Explain the difference between authentication and authorization with an example.
Think about logging into a website and what you can do after logging in.
You got /3 concepts.
    Why should authentication and authorization be handled separately in system design?
    Consider what happens if you mix verifying identity and checking permissions.
    You got /3 concepts.