Easy DVC Question 56 of 221

Why should large datasets not live directly in Git?

MLOps track · Speak this in 60–90 seconds · Faridabad & Delhi NCR

PICTURE THIS: HASH MAP

Key"user_id"
Hashslot 17
Valuethe record

Simple meaning

Git is designed for small text diffs, not multi-gigabyte Parquet dumps.

1

WHY — DVC instead of guessing?

Why interviewers care about DVC:

They are checking judgment

on DVC.

A good answer names

the situation, the default choice, and one exception - that reads as experience.

Stay structured

Name the idea, why it exists, then one short example.

Close cleanly

End with when you use it and one common pitfall.

2

STEPS — What happens step by step?

Before you speak the answer, walk the interviewer through these steps:

  1. 1
    Git is designed for

    small text diffs, not multi-gigabyte Parquet dumps.

  2. 2
    Repos become slow and

    clones become painful.

  3. 3
    DVC or object storage

    with hashes keeps Git usable while still versioning data.

  4. 4
    Give an example

    One tiny concrete case you can say aloud.

  5. 5
    Common mistake

    What juniors usually get wrong.

  6. 6
    Close

    When you pick this over the alternative.

3

EXAMPLE — See it in action

Here's a short line you can speak, broken into clear beats:

Say this line
“Repos become slow and clones become painful.”
Break into beats
Reposbecomeslowandclonesbecome
Speaking order
2987408337471632900

Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.

Key takeaway

Git is designed for small text diffs, not multi-gigabyte Parquet dumps. Repos become slow and clones become painful.

Chat with us