Concept questionMedium~7 minContainers & Runtime Essentials / 11 of 15

Interview question

Where should a containerized .NET application store logs, uploads, temporary files, caches, and durable business data?

Container filesystems, volumes, state, and logging

Separates ephemeral instance files from durable data and sends logs, uploads, caches, and diagnostics to storage with explicit lifecycle ownership.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

Durable business data belongs in a database, object store, or deliberately managed persistent volume rather than the container's writable layer. Application logs normally go to stdout and stderr so the platform can collect, index, retain, and rotate them. User uploads usually belong in object storage when replicas need shared access. Temporary files can use an explicit ephemeral directory with quotas and cleanup. A local cache is acceptable only when losing it is safe and each replica can rebuild it.

Full answer below

Practice focus

Writable layers, ephemeral storage, volumes, object storage, databases, stdout, rotation, replicas, and cleanup.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Why this question matters
The container's writable layer is tied to that instance and can disappear on replacement. Durable business data must live in a database, object store, or deliberately managed persistent volume.
Durable business data belongs in a database, object store, or deliberately managed persistent volume rather than the container's writable layer. Application logs normally go to stdout and stderr so the platform can collect, index, retain, and rotate them. User uploads usually belong in object storage when replicas need shared access. Temporary files can use an explicit ephemeral directory with quotas and cleanup. A local cache is acceptable only when losing it is safe and each replica can rebuild it.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
Persistent volumes are useful when the workload genuinely needs filesystem semantics, but they introduce attachment, access-mode, backup, and multi-replica constraints. I would not attach one writable disk to several replicas without understanding the storage contract. Crash dumps or diagnostic traces can be written to a bounded diagnostic volume or streamed to platform tooling. Sensitive temporary data needs permissions and deletion behavior just like durable data.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
In production I monitor ephemeral disk usage because a filled filesystem can crash an otherwise healthy service. Log collection has backpressure and outage behavior; synchronous remote logging must not block every request. Storage choice follows consistency, durability, access pattern, and recovery requirements rather than convenience. Backups and restore tests cover persistent data, while instance replacement tests confirm no essential state was hidden locally. A cleanup owner exists for temporary objects, abandoned uploads, and diagnostic artifacts.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Writing application logs only to a file inside the container.
Storing uploads on one replica's writable layer.
Treating every volume as automatically durable and backed up.
Creating temporary files without quotas or cleanup.

Red flagsCandidateSigns the container design is fragileSignals that an interviewer may treat as risky.Open details

Details

Replacing a replica loses customer data.
Disk usage grows without an owner.
Multiple replicas assume local files are shared.
Logging failure blocks request processing.

Follow-up prompts

Quick interviewer prompts inside this drill.

Follow-up questionsCandidateFollow-up questionsLikely next questions after the main answer.Open details

Details

Treat these as the next interviewer turn. Answer one out loud, then save the gap in your practice notes.

When would you use a persistent volume?
Why prefer stdout for logs?
Where should crash dumps be written?

Continue the section

Next in Containers & Runtime Essentials: Docker Compose locally

Step 12 of 15

Docker Compose for local multi-service development

Opening drill

Concept questionMedium~7 minContainers & Runtime Essentials / 11 of 15

Interview question

Where should a containerized .NET application store logs, uploads, temporary files, caches, and durable business data?

Container filesystems, volumes, state, and logging

Separates ephemeral instance files from durable data and sends logs, uploads, caches, and diagnostics to storage with explicit lifecycle ownership.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

Full answer below

Practice focus

Writable layers, ephemeral storage, volumes, object storage, databases, stdout, rotation, replicas, and cleanup.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Why this question matters
The container's writable layer is tied to that instance and can disappear on replacement. Durable business data must live in a database, object store, or deliberately managed persistent volume.
Durable business data belongs in a database, object store, or deliberately managed persistent volume rather than the container's writable layer. Application logs normally go to stdout and stderr so the platform can collect, index, retain, and rotate them. User uploads usually belong in object storage when replicas need shared access. Temporary files can use an explicit ephemeral directory with quotas and cleanup. A local cache is acceptable only when losing it is safe and each replica can rebuild it.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
Persistent volumes are useful when the workload genuinely needs filesystem semantics, but they introduce attachment, access-mode, backup, and multi-replica constraints. I would not attach one writable disk to several replicas without understanding the storage contract. Crash dumps or diagnostic traces can be written to a bounded diagnostic volume or streamed to platform tooling. Sensitive temporary data needs permissions and deletion behavior just like durable data.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
In production I monitor ephemeral disk usage because a filled filesystem can crash an otherwise healthy service. Log collection has backpressure and outage behavior; synchronous remote logging must not block every request. Storage choice follows consistency, durability, access pattern, and recovery requirements rather than convenience. Backups and restore tests cover persistent data, while instance replacement tests confirm no essential state was hidden locally. A cleanup owner exists for temporary objects, abandoned uploads, and diagnostic artifacts.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Writing application logs only to a file inside the container.
Storing uploads on one replica's writable layer.
Treating every volume as automatically durable and backed up.
Creating temporary files without quotas or cleanup.

Red flagsCandidateSigns the container design is fragileSignals that an interviewer may treat as risky.Open details

Details

Replacing a replica loses customer data.
Disk usage grows without an owner.
Multiple replicas assume local files are shared.
Logging failure blocks request processing.

Follow-up prompts

Quick interviewer prompts inside this drill.

Follow-up questionsCandidateFollow-up questionsLikely next questions after the main answer.Open details

Details

Treat these as the next interviewer turn. Answer one out loud, then save the gap in your practice notes.

When would you use a persistent volume?
Why prefer stdout for logs?
Where should crash dumps be written?

Continue the section

Next in Containers & Runtime Essentials: Docker Compose locally

Step 12 of 15

Docker Compose for local multi-service development

Where should a containerized .NET application store logs, uploads, temporary files, caches, and durable business data?

Practice focus

Answer path

Why this question matters

Review signals

Follow-up prompts

Continue the section

Where should a containerized .NET application store logs, uploads, temporary files, caches, and durable business data?

Practice focus

Answer path

Why this question matters

Review signals

Follow-up prompts

Continue the section