The answer is to enable sticky sessions on the load balancer. This configuration, also known as session affinity, ensures that all requests from a single user during a session are routed to the same backend instance, which is critical during auto-scaling events when new instances are spun up or old ones are terminated. Without sticky sessions, a load balancer using a round-robin or least-connections algorithm could direct a returning user to a different instance after a scale-out, causing the loss of any in-memory session state. On the CompTIA Cloud+ CV0-004 exam, this tests your understanding of how to maintain session persistence in a hybrid cloud environment with dynamic scaling across availability zones. A common trap is assuming that auto-scaling alone handles session data, but it does not—sticky sessions are the explicit mechanism. Memory tip: “Stick to the same instance to keep the session consistent.”
CV0-004 Deployment Practice Question
This CV0-004 practice question tests your understanding of deployment. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A company is deploying a new web application in a hybrid cloud environment. The application must be highly available and able to handle traffic spikes. The cloud team decides to use an auto-scaling group across multiple availability zones with a load balancer. Which additional step should the team take to ensure session persistence during scaling events?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Enable sticky sessions on the load balancer
Sticky sessions (also known as session affinity) ensure that all requests from a user during a session are directed to the same backend instance. In an auto-scaling group, instances are added or removed dynamically; without sticky sessions, a load balancer using a default algorithm could route a user to a different instance after a scale-out event, losing the in-memory session state. Enabling sticky sessions on the load balancer preserves session persistence across scaling events by binding the user's session to a specific instance for its duration.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Implement a stateless application design
Why it's wrong here
While good practice, it may not be feasible for existing applications.
✗
Increase the instance size to handle more sessions
Why it's wrong here
Scaling vertically does not ensure session persistence.
✗
Configure the load balancer to use a round-robin algorithm
Why it's wrong here
Round-robin distributes requests without session affinity.
✓
Enable sticky sessions on the load balancer
Why this is correct
Sticky sessions maintain session affinity during scaling.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse high availability with session persistence, assuming that distributing traffic evenly (round-robin) or scaling instances is sufficient, but they overlook that stateful applications require session affinity to maintain user context during dynamic scaling events.
Detailed technical explanation
How to think about this question
Sticky sessions are typically implemented using cookies (e.g., AWS Application Load Balancer generates a cookie named AWSALB) or by the load balancer inspecting source IP addresses. Under the hood, the load balancer maintains a mapping of session identifiers to backend instances; when an instance is terminated during scale-in, sessions on that instance are lost unless the application uses external session storage (e.g., Redis or a database). In a hybrid cloud environment, sticky sessions can also be configured on on-premises load balancers like F5 BIG-IP using persistence profiles, which must be coordinated with the cloud auto-scaling group to avoid routing to terminated instances.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A practitioner preparing for the CV0-004 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Deployment — This question tests Deployment — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Enable sticky sessions on the load balancer — Sticky sessions (also known as session affinity) ensure that all requests from a user during a session are directed to the same backend instance. In an auto-scaling group, instances are added or removed dynamically; without sticky sessions, a load balancer using a default algorithm could route a user to a different instance after a scale-out event, losing the in-memory session state. Enabling sticky sessions on the load balancer preserves session persistence across scaling events by binding the user's session to a specific instance for its duration.
What should I do if I get this CV0-004 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This CV0-004 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CV0-004 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.