Any concept.
clear in 60 seconds.

Hashing is one-way for verification, while encryption is two-way for confidentiality.

Secure API design requires multiple strategies to protect sensitive data and access.

Authentication verifies who you are, while authorization determines what you can do.

Zero Trust Architecture ensures that no user or device is trusted by default.

SSRF is a vulnerability where an attacker tricks a server into making unintended requests.

Session-based authentication uses cookies to remember users after login.

CSRF tricks your browser into making requests without your consent.

Encryption at rest and in transit are essential for protecting data both stored and in motion.

Symmetric encryption uses one key, while asymmetric uses a pair of keys for security.

XSS is a vulnerability that lets attackers run scripts in users' browsers.

HTTPS is a secure version of HTTP that encrypts data for safety.

The TLS handshake establishes a secure connection for HTTPS, ensuring data safety.

KMS securely manages encryption keys to protect data from theft.

Fail Fast means stopping quickly on errors, while Fail Safe ensures safety in failures.

Password hashing with unique salts ensures security by creating different hashes for identical passwords.

Container networking enables communication between services in different containers.

Availability is about access; reliability is about correct performance.

API keys help identify clients and control their access to APIs securely.

mTLS allows microservices to verify each other's identities using certificates.

SQL injection is a security risk where attackers manipulate database queries via input fields.

Disaster recovery ensures systems can restore services and data after major disruptions.

Dependency failures can disrupt applications, but resilience patterns can help manage them.

The CAP Theorem explains the trade-offs in distributed systems during network failures.

OAuth 2.0 lets apps access user data securely without passwords.

DNS resolution translates a URL into an IP address for web access.

Cache penetration occurs when requests for non-existent data overload the database.

Crash failures stop a service, while network failures disrupt communication.

A single component's failure can take down your entire application, even with redundancy.

The TCP 3-way handshake ensures reliable connection establishment between a client and server.

FAANG interviewers evaluate problem understanding, architecture, scalability, and communication skills.

The Bulkhead Pattern isolates resources to protect critical workloads from failures.

Token expiration and refresh token rotation secure user sessions by limiting token lifespan and preventing unauthorized access.

JWTs allow secure user authentication without needing session storage.

Access tokens are short-lived tokens for API access, while refresh tokens renew them without re-login.

Fault domains help prevent multiple servers from failing together in an architecture.

Disaster Recovery Testing verifies that your recovery plan works effectively in real situations.

Fallbacks allow systems to handle failures safely and maintain user experience.

Failover ensures systems remain operational by managing leader changes during failures.

Cassandra uses a masterless architecture to distribute and replicate data efficiently.

Choosing the right boundaries for microservices is crucial for effective architecture.

A Circuit Breaker helps prevent system failures by stopping calls to unhealthy services.

A CDN speeds up web applications by caching content closer to users.

API Gateway, Proxy, and Load Balancer serve different roles in managing requests and traffic in systems.

Functional requirements define what a system does, while non-functional requirements define how it performs.

Alerting helps notify the right people about production issues quickly.