mediumMultiple Choice
CV0-004 Practice Question: Migrating a legacy application to the cloud using…
A company is migrating a legacy application to the cloud using a replatforming strategy. The application uses a proprietary logging framework that writes logs to local disk. The cloud architecture uses ephemeral storage for the application servers. The operations team notices that logs are lost when servers are replaced during auto-scaling events. What is the best solution to ensure logs are preserved?
⚠ Common exam trap
Candidates often think increasing storage or optimizing local I/O solves the persistence problem, but the exam tests understanding that ephemeral storage is inherently non-persistent and that logs must be sent off-instance to survive instance replacement.
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
✓
Configure the logging framework to write to a central log server over the network.
The core issue is that ephemeral storage is lost when instances are terminated or replaced during auto-scaling events. By configuring the logging framework to write to a central log server over the network (e.g., using syslog, HTTP, or a dedicated log aggregation service), logs are persisted independently of the application server's lifecycle. This decouples log storage from compute resources, ensuring logs survive scaling events.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Increase the size of the ephemeral storage.
Why it's wrong here
Ephemeral disks are destroyed with the instance, so enlarging them only delays loss until the next auto-scaling replacement; the logs still vanish. Larger ephemeral volumes suit scratch data or caches that tolerate deletion, not audit trails requiring persistence beyond instance lifetime.
- ✗
Use memory-only logging to speed up disk I/O.
Why it's wrong here
Memory-only logging is volatile: buffers are erased when the instance terminates, so auto-scaling replacements lose everything, and memory pressure can drop entries mid-run. It suits high-throughput transient debugging where durability is irrelevant, not logs that must survive instance replacement.
- ✗
Disable auto-scaling for the application servers.
Why it's wrong here
Disabling auto-scaling removes the elasticity the replatforming strategy depends on and does not preserve logs already written to ephemeral disk when a server is replaced. It is tempting because it stops the loss events, and would be correct only where scaling is genuinely unnecessary and downtime acceptable.
- ✓
Configure the logging framework to write to a central log server over the network.
Why this is correct
Ephemeral storage is destroyed when auto-scaling replaces instances, so local log files vanish. Redirecting the proprietary framework to write over the network to a central log server decouples log retention from instance lifecycle, preserving all entries.
Go deeper
Related to this question
About these practice questions
This CV0-004 question is part of Courseiva's 834-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.