TTechclick ⚡ XP 0% All lessons
HAProxy · Load Balancing · ACLs / Stick TablesInteractive · L1 / L2 / L3

HAProxy — Frontends, Backends and ACL Decisions

HAProxy is fast, explicit and configuration-driven: frontends receive traffic, ACLs classify requests, backends carry server pools, and stick tables/metrics make rate limits and troubleshooting visible. This lesson gives you a production mental model.

📅 2026-06-22 · ⏱ 17 min · 5 infographics · scenario lab · 🏷 10-Q assessment + AI Tutor inline

⚡ Quick Answer

Interactive HAProxy lesson: frontends, backends, ACLs, TLS bind, stick tables, rate controls, health checks and Prometheus metrics.

🎯 By the end you will be able to

Read as:

Pick where you want to start

1

What it solves

Use it for high-performance L4/L7 load balancing, routing decisions, TLS termination and programmable traffic policy.

 2

Core objects

Name the pieces before you troubleshoot.

 3

Traffic path

Follow one request through the decision chain.

 4

Ops & interview

Failure, evidence, fix and verification.

🧠 Warm-up — 3 questions, no score

Just notice which ones make you pause. We answer all three inside the lesson.

1. What is the fastest way to avoid vague HAProxy answers?

Answered in Traffic path.

2. What proves a policy decision in production?

Answered in Ops & interview.

3. What is the safest rollout pattern?

Answered in Ops & interview.

Most engineers think...

Most candidates describe HAProxy Frontends, Backends and ACLs as a product name and stop there. That is not enough for L2/L3 work.

The better model is operational: know the components, follow the flow, prove the policy hit, and explain the failure path. For this topic, the core idea is frontend, ACL rule, backend and stick table.

① What it solves and where it sits

Do not answer HAProxy as just round-robin. The interview path is listener, ACL, action, backend, health check, log/metric, and stick-table state if abuse control is involved.

Production use case: Use it for high-performance L4/L7 load balancing, routing decisions, TLS termination and programmable traffic policy.

Figure 1 — HAProxy Frontends, Backends and ACLs healthy flow
Start with this path when explaining or troubleshooting.HAProxy Frontends, Backends and ACLs healthy flowClient hits bidecision pointFrontend ACLsdecision pointAction selectsdecision pointHealth gatedecision pointServer + metridecision point
Start with this path when explaining or troubleshooting.
Quick check · Q1 of 10 · Understand

Best one-line description of HAProxy Frontends, Backends and ACLs?

Correct: b. The core is frontend, ACL rule, backend and stick table; explain the architecture and evidence path, not only the product name.
👉 So far: HAProxy Frontends, Backends and ACLs solves Use it for high-performance L4/L7 load balancing, routing decisions, TLS termination and programmable traffic policy..

② Core components you must name

Use these names before jumping to troubleshooting. They anchor the architecture and make the interview answer sound practical.

Figure 2 — Component stack
The named objects/components that carry the design.Component stackfrontendListener that accepts client connectionsbackendPool of servers plus load-balancing policyACLCondition matching request or connection attributesTLS bindCertificate-enabled listener for HTTPS terminationStick tableIn-memory counters/tags for rate limiting or affinity logic
The named objects/components that carry the design.
🧭
Flow first
tap to flip

Say the path in order: Client hits bind → Frontend ACLs → Action selects backend → Health gate → Server + metrics. It keeps the answer structured.

🛡
Policy proof
tap to flip

A decision is not real until logs/events show the rule, object and final action.

🔧
Health gate
tap to flip

Most outages are not product magic; they are forwarding, health, identity, certificate or rule-order problems.

📊
Rollout
tap to flip

Safe rollout: Validate frontends/backends first, add ACLs in log-only style, then enforce denies or rate limits with metrics watched.

Name objects before tools

Lead with frontend, backend, ACL. It sounds like production work, not brochure reading.

Quick check · Q2 of 10 · Remember

Which item belongs in the core architecture?

Correct: c. frontend is one of the named components you should use in a precise answer.
👉 So far: Core components: frontend, backend, ACL, TLS bind.

③ The traffic or telemetry path

The healthy path is: Client hits bind → Frontend ACLs → Action selects backend → Health gate → Server + metrics. Walk it left to right. If a user report says 'it is broken', locate the exact stage where evidence stops.

The primary control is: Route or deny traffic based on ACLs, backend health and stick-table counters.

Figure 3 — Policy and evidence hub
Good troubleshooting ties every path back to policy, health and logs.Policy and evidence hubPolicy + logstruth sourcefrontendbackendACLTLS bindStick table
Good troubleshooting ties every path back to policy, health and logs.
Figure 4 — Healthy versus broken path
The right side is the classic failure you should catch quickly.Healthy versus broken pathHealthyTraffic is steered correctlyPolicy/object health is validLogs show final actionUser impact is scopedBrokenThe ACL match is too broad or theEvidence stops earlyUsers see inconsistent resultsFix needs verification
The right side is the classic failure you should catch quickly.
Do not skip the first hop

If Client hits bind never reaches the control point, no later policy can help. Confirm steering/forwarding first.

▶ Watch the HAProxy Frontends, Backends and ACLs decision path

Press Play for the healthy path, then Break it for the common outage.

① Client hits bindClient hits bind: HAProxy Frontends, Backends and ACLs advances this stage and records evidence for troubleshooting.
▼
② Frontend ACLsFrontend ACLs: HAProxy Frontends, Backends and ACLs advances this stage and records evidence for troubleshooting.
▼
③ Action selects backendAction selects backend: HAProxy Frontends, Backends and ACLs advances this stage and records evidence for troubleshooting.
▼
④ Health gateHealth gate: HAProxy Frontends, Backends and ACLs advances this stage and records evidence for troubleshooting.
Press Play to step through the healthy path. Then press Break it.
Quick check · Q3 of 10 · Apply

What should you trace first during troubleshooting?

Correct: a. Start at Client hits bind and follow the flow until evidence stops.
👉 So far: Healthy flow: Client hits bind → Frontend ACLs → Action selects backend → Health gate → Server + metrics.

④ Operations, rollout and interview response

The safe rollout answer is: Validate frontends/backends first, add ACLs in log-only style, then enforce denies or rate limits with metrics watched. That prevents broad production impact while still moving toward enforcement.

Compared with a black-box load balancer GUI, the value is richer policy context, better visibility and a clearer operational evidence trail.

Figure 5 — Interview troubleshooting path
Use this sequence to avoid random guessing.Interview troubleshooting pathConfirmscope + symptomTraceflow stageCheckpolicy + healthFixsmall changeVerifylogs + user test
Use this sequence to avoid random guessing.

Rohan at a Noida SOC gets this ticket

A new ACL intended for admin paths blocks normal users after deployment.

Likely cause

The ACL match is too broad or the action order catches traffic before a more specific rule.

Diagnosis

Trace Client hits bind → Frontend ACLs → Action selects backend → Health gate → Server + metrics, then compare policy logs, object health and user scope.

Console ▸ policy/logs ▸ health/status ▸ affected user test
Fix

Check rule order, ACL sample fetches, logs, backend selection, and add Prometheus/statistics validation before enforcement.

Verify

Repeat the original user test and capture the allow/block/health evidence in logs.

Close with proof

The final answer should include log evidence, health state and a user test. That is what separates RCA from guessing.

Quick check · Q4 of 10 · Evaluate

Safest production rollout answer?

Correct: d. A controlled pilot with monitoring and verification reduces blast radius while building confidence.
👉 So far: Classic failure: The ACL match is too broad or the action order catches traffic before a more specific rule.

🤖 Ask the AI Tutor

Tap any question — instant, scoped to this lesson. No login, no waiting.

Pre-curated from vendor docs + community Q&A, scoped to this lesson. For a live prod issue, paste your export into chat.techclick.in.

📝 Wrap-up assessment — six more

You've answered 4 inline. Six left. 70% (7 of 10) marks the lesson complete on your profile. Tap Submit all answers at the end.

Q5 · Remember

What should you name before troubleshooting?

Correct: b. Naming objects and flow prevents random guessing.
Q6 · Understand

What proves a policy decision?

Correct: a. Logs/events prove rule match, action, object and user context.
Q7 · Apply

Where should you start tracing HAProxy Frontends, Backends and ACLs?

Correct: c. Start at Client hits bind and move stage by stage.
Q8 · Analyze

Why is a pilot safer than global enforcement?

Correct: b. Pilot scope lets you catch false positives or broken forwarding before broad impact.
Q9 · Evaluate

Best interview closing line?

Correct: d. Verification is the only defensible close to a production troubleshooting answer.
Q10 · Evaluate

What is the likely root cause in this lesson's scenario: A new ACL intended for admin paths blocks normal users after deployment.

Correct: c. The ACL match is too broad or the action order catches traffic before a more specific rule.
Lesson complete — saved to your profile.
Almost! You need 70% (7 of 10) — re-read the path that tripped you up and tap "Try again".

🧠 In your own words

Explain HAProxy Frontends, Backends and ACLs in one L2 interview sentence.

Expert version: HAProxy Frontends, Backends and ACLs should be explained by the flow Client hits bind → Frontend ACLs → Action selects backend → Health gate → Server + metrics, the core control frontend, ACL rule, backend and stick table, and the proof points: policy logs, health state and user verification.

🗣 Teach a friend

Best way to lock it in — explain it in one line to a teammate. Tap to generate a paste-ready summary.

📖 Glossary

frontend
HAProxy listener section that accepts client connections.
backend
Section containing server pools and load-balancing behavior.
ACL
Access control list condition used to trigger routing or security actions.
bind ssl crt
Listener syntax for TLS termination using a certificate.
Stick table
In-memory table tracking client/server counters or tags.
Prometheus exporter
HAProxy metrics endpoint for monitoring and alerting.

📚 Sources

  1. HAProxy backends
  2. HAProxy ACLs
  3. HAProxy TLS basics
  4. HAProxy stick tables
  5. HAProxy Prometheus metrics

What's next?

Next, pair this lesson with the new HAProxy Frontends, Backends and ACLs interview Q&A page and explain the same flow out loud in 90 seconds.

Next · All interview lessons → Practice on exam.techclick.in →