easyMultiple Choice
CV0-004 Practice Question: A cloud administrator needs to deploy a new…
A cloud administrator needs to deploy a new application that requires a static IP address. The administrator is using a cloud provider that allows the reservation of elastic IP addresses. Which deployment step should be taken to ensure the IP address is not lost when the resource is stopped?
⚠ Common exam trap
CompTIA often tests the distinction between ephemeral public IPs (which are lost on stop/start) and elastic/reserved IPs (which persist), and the trap here is that candidates may confuse a static private IP (Option C) with a static public IP, or think DNS alone (Option D) can prevent IP loss.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Allocate an elastic IP address and associate it with the resource.
Elastic IP addresses are static public IPv4 addresses that you can allocate to your account and associate with a resource. When you associate an elastic IP with an instance, it persists even if the instance is stopped, because the IP is reserved in your account until you explicitly release it. This ensures the IP address is not lost when the resource is stopped, unlike ephemeral public IPs that change on stop/start.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Configure the instance to obtain an IP via DHCP.
Why it's wrong here
DHCP assigns addresses dynamically, so a stopped instance may return with a different address, defeating the static-IP requirement. It is tempting because DHCP is the default configuration, but the correct step is associating a reserved elastic IP with the instance so the address persists across stop and start cycles.
- ✓
Allocate an elastic IP address and associate it with the resource.
Why this is correct
Elastic IP addresses are reserved, account-level public addresses that persist independently of any instance lifecycle. Associating one with the resource means stopping or restarting it preserves the same static public IP, satisfying the no-loss constraint.
- ✗
Assign a private IP address from a reserved range.
Why it's wrong here
A private address from a reserved range is not routable on the internet, so it cannot serve as the application's public static endpoint. Reserved private ranges suit internal-only tiers behind NAT. The scenario requires an elastic public IP that persists across stop/start, which this step does not deliver.
- ✗
Set up an external DNS service to point to the public IP.
Why it's wrong here
External DNS merely maps a name to whatever public IP the instance currently holds; when the resource stops and the address is released, the record points to a stale or reassigned address. DNS is for name resolution and traffic steering, not for retaining an elastic IP allocation across stop/start cycles.
Visual reference
Go deeper
Related to this question
About these practice questions
Courseiva writes every CV0-004 question from scratch — 834 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.