Why infrastructure design underpins everything in HLD - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why is infrastructure design critical for system reliability?

Consider a web application that experiences frequent downtime. Which infrastructure design aspect most directly improves its reliability?

A Implementing redundant servers and failover mechanisms

B Reducing the number of users accessing the system

C Deploying the application only on a local machine

D Using a single powerful server with high CPU and memory

💡 Hint

Think about how to keep the system running even if one part fails.

Redundancy and failover ensure that if one server fails, others take over, improving reliability.

❓ Architecture

intermediate

Which infrastructure design best supports scalability?

You expect your system's user base to grow rapidly. Which infrastructure design choice best supports this growth?

A Using horizontal scaling with load balancers and multiple servers

B Limiting the number of concurrent users

C Designing a monolithic server that handles all requests

D Deploying the system on a single cloud instance

💡 Hint

Think about adding more machines to handle more users.

Horizontal scaling with load balancers distributes traffic across servers, allowing growth.

❓ scaling

advanced

What is the main tradeoff when choosing between vertical and horizontal scaling?

When designing infrastructure, what is the primary tradeoff between vertical scaling (upgrading a single server) and horizontal scaling (adding more servers)?

A Vertical scaling eliminates downtime; horizontal scaling increases downtime

B Vertical scaling requires more servers; horizontal scaling requires fewer servers

C Vertical scaling improves network speed; horizontal scaling reduces CPU usage

D Vertical scaling is cheaper but less flexible; horizontal scaling is more complex but more scalable

💡 Hint

Consider cost, complexity, and flexibility.

Vertical scaling upgrades one server, cheaper but limited; horizontal scaling adds servers, more complex but scales better.

❓ tradeoff

advanced

Which infrastructure design choice impacts system latency the most?

To reduce latency for users worldwide, which infrastructure design choice is most effective?

A Increasing the CPU speed of the central server

B Using a single central data center for all users

C Deploying servers in multiple geographic regions (edge locations)

D Reducing the number of database queries

💡 Hint

Think about physical distance between users and servers.

Deploying servers closer to users reduces network travel time, lowering latency.

❓ estimation

expert

Estimate the infrastructure capacity needed for 1 million daily active users

Your system expects 1 million daily active users, each making an average of 10 requests per day. Each server can handle 10 requests per second. Estimate the minimum number of servers needed to handle peak load assuming peak traffic is 10% of daily requests concentrated in one hour.

A 12 servers

B 28 servers

C 60 servers

D 36 servers

💡 Hint

Calculate total requests per peak hour, then divide by server capacity.

1 million users * 10 requests = 10 million requests/day. Peak 10% in 1 hour = 1 million requests in 3600 seconds ≈ 278 requests/sec. Each server handles 10 requests/sec, so servers needed ≈ 278 / 10 = 28 servers.

Practice

1. Why is infrastructure design considered the foundation of all system parts?

easy

A. Because it ensures the system is reliable, scalable, and maintainable

B. Because it only focuses on the user interface design

C. Because it ignores future growth and changes

D. Because it is only about hardware setup

Solution

1. Step 1: Understand the role of infrastructure design

   Infrastructure design sets the base for how all parts of a system work together, affecting reliability and scalability.

2. Step 2: Identify why it matters for system parts

   Good infrastructure design supports system growth, performance, and maintenance, unlike options that focus narrowly on UI or hardware only.

3. Final Answer:

   Because it ensures the system is reliable, scalable, and maintainable -> Option A

4. Quick Check:

   Infrastructure design = foundation for reliability and scalability [OK]

Hint: Think of infrastructure as the system's strong base [OK]

Common Mistakes:

• Confusing infrastructure with just UI design
• Ignoring scalability and future growth
• Thinking infrastructure is only hardware

2. Which of the following is a correct statement about infrastructure design?

easy

A. It helps in making the system scalable and reliable

B. It is unrelated to system performance

C. It should be planned only after the system is fully built

D. It only deals with choosing colors and fonts

Solution

1. Step 1: Review the purpose of infrastructure design

   Infrastructure design is about planning system components to ensure performance and scalability.

2. Step 2: Evaluate each option's correctness

   Only It helps in making the system scalable and reliable correctly states that infrastructure design helps scalability and reliability; others are false or irrelevant.

3. Final Answer:

   It helps in making the system scalable and reliable -> Option A

4. Quick Check:

   Infrastructure design = scalability and reliability [OK]

Hint: Infrastructure design improves system growth and stability [OK]

Common Mistakes:

• Thinking infrastructure is a late task
• Ignoring its impact on performance
• Confusing it with UI styling

3. Consider a system designed without proper infrastructure planning. Which of the following outcomes is most likely?

medium

A. The system will be fast and easily scalable

B. The system will have perfect security by default

C. The system may face frequent failures and slowdowns

D. The system will automatically fix design issues

Solution

1. Step 1: Analyze effects of poor infrastructure design

   Poor planning often leads to unreliable systems with performance issues and failures.

2. Step 2: Match outcomes to options

   The system may face frequent failures and slowdowns correctly describes likely failures and slowdowns; other options are unrealistic or incorrect.

3. Final Answer:

   The system may face frequent failures and slowdowns -> Option C

4. Quick Check:

   Poor infrastructure = failures and slowdowns [OK]

Hint: Bad infrastructure causes failures, not fixes [OK]

Common Mistakes:

• Assuming system auto-fixes design flaws
• Believing poor design leads to perfect security
• Thinking poor design improves speed

4. A team built a system without considering infrastructure design. The system crashes under load. What is the most likely cause?

medium

A. They used too many colors in the UI

B. They did not plan for scalability and resource management

C. They wrote too many comments in code

D. They chose the wrong font style

Solution

1. Step 1: Identify cause of crashes under load

   Crashes under load usually happen due to poor scalability and resource planning in infrastructure.

2. Step 2: Evaluate options for relevance

   Only They did not plan for scalability and resource management relates to infrastructure and system stability; others are unrelated UI or code style issues.

3. Final Answer:

   They did not plan for scalability and resource management -> Option B

4. Quick Check:

   Crashes under load = poor scalability planning [OK]

Hint: Crashes under load? Check scalability plans first [OK]

Common Mistakes:

• Blaming UI colors for system crashes
• Confusing code comments with performance
• Ignoring resource management importance

5. You are designing a new online service expected to grow rapidly. Which infrastructure design choice best supports this growth?

hard

A. Build a single server system with fixed resources

B. Use outdated hardware to reduce initial expenses

C. Ignore monitoring and logging to save costs

D. Design a scalable architecture with load balancing and auto-scaling

Solution

1. Step 1: Understand requirements for rapid growth

   Rapid growth requires infrastructure that can scale automatically and balance load to maintain performance.

2. Step 2: Evaluate each option against growth needs

   Design a scalable architecture with load balancing and auto-scaling supports scalability and reliability; others limit growth or risk failures.

3. Final Answer:

   Design a scalable architecture with load balancing and auto-scaling -> Option D

4. Quick Check:

   Rapid growth needs scalable, balanced infrastructure [OK]

Hint: Choose scalable, auto-scaling infrastructure for growth [OK]

Common Mistakes:

• Choosing fixed resource servers for growing systems
• Skipping monitoring which helps detect issues
• Using outdated hardware risking failures