The correct answer is to configure end-to-end encryption using HTTPS between the load balancer and backend instances. This design change is necessary because the cloud provider’s load balancer typically terminates the client’s TLS connection, then forwards traffic to backend servers over unencrypted HTTP, which violates the requirement that all data must be encrypted in transit. By enforcing HTTPS on the internal path, you ensure that the entire data flow—from client to load balancer to backend—remains encrypted, satisfying both in-transit and at-rest compliance mandates. On the CompTIA Cloud+ CV0-004 exam, this scenario tests your understanding of how load balancers handle TLS termination and the common pitfall of assuming internal network traffic is automatically secure. A frequent trap is thinking that encryption at the load balancer alone is sufficient, but the exam emphasizes that any decrypted traffic traversing the internal network must also be protected. Memory tip: think “TLS to the wall, then HTTPS down the hall”—encrypt every hop, not just the front door.
CV0-004 Cloud Architecture and Design Practice Question
This CV0-004 practice question tests your understanding of cloud architecture and design. 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 uses a public cloud provider and has a requirement that all data must be encrypted in transit and at rest. The architect notices that the cloud provider's load balancer terminates TLS and forwards traffic to backend instances over HTTP. Which design change should the architect make?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Configure end-to-end encryption using HTTPS between load balancer and backend
Option D is correct because the requirement mandates encryption in transit for all data paths. By configuring end-to-end HTTPS between the load balancer and backend instances, the architect ensures that traffic is encrypted from the client to the backend, even after the load balancer terminates the initial TLS connection. This prevents plaintext HTTP traffic from flowing over the internal network, satisfying the encryption-at-rest and in-transit compliance needs.
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 web application firewall (WAF) on the backend
Why it's wrong here
WAF provides security but does not encrypt traffic; it inspects packets.
✗
Enable TLS termination at the backend instances only
Why it's wrong here
That would not change the load balancer configuration; traffic to load balancer still terminates TLS.
✗
Use a VPN tunnel between the load balancer and backend
Why it's wrong here
A VPN adds encryption but is more complex; the simpler solution is to use HTTPS on backend.
✓
Configure end-to-end encryption using HTTPS between load balancer and backend
Why this is correct
This ensures traffic is encrypted all the way from client to backend instance.
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 assume TLS termination at the load balancer is sufficient for encryption in transit, overlooking that the requirement applies to the entire data path, including the segment between the load balancer and backend instances.
Detailed technical explanation
How to think about this question
End-to-end encryption with HTTPS between the load balancer and backend typically involves configuring the load balancer to re-encrypt traffic using a new TLS session (often with a self-signed certificate or a private CA) before forwarding to backend instances. This ensures that even if the load balancer terminates the client's TLS, the data remains encrypted over the internal network, preventing exposure from internal sniffing or misconfigured network segments. In AWS, this is achieved by using an Application Load Balancer with HTTPS listeners and HTTPS target groups, while in Azure it involves configuring Application Gateway with backend HTTPS settings.
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 small business has 20 workstations on the 192.168.1.0/24 network and one public IP from its ISP. The router uses PAT (NAT overload) so all 20 devices share one public address using different source ports. NAT questions test whether you understand the four address terms and which direction each translation applies.
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.
Cloud Architecture and Design — This question tests Cloud Architecture and Design — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Configure end-to-end encryption using HTTPS between load balancer and backend — Option D is correct because the requirement mandates encryption in transit for all data paths. By configuring end-to-end HTTPS between the load balancer and backend instances, the architect ensures that traffic is encrypted from the client to the backend, even after the load balancer terminates the initial TLS connection. This prevents plaintext HTTP traffic from flowing over the internal network, satisfying the encryption-at-rest and in-transit compliance needs.
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.