advanced / August 2026

Martech Exit Risk and Data Control Advanced Quiz

Martech decisions can become hard to reverse when data, workflows, and suppliers are locked in. Review exit risk, open formats, rented data, supplier reassessment, suppression durability, and data minimisation before renewal or selection.

Before you start

Start a 10-question practice round.

Sign in before starting if you want a leaderboard score.

New

Sign in to get ranked
Questions
10
Time limit
9 min
Scoring
First signed-in attempt counts
Edition
August 2026

What this quiz checks

Keep martech decisions portable without blocking useful progress

Martech exit planningData portabilityOpen standards reviewSupplier due diligenceData minimisation
  • Balance Speed Against Exit RiskA fast tool choice may still be reasonable, but advanced operations work makes the switching cost visible before the team commits.
  • Protect Data PortabilityData control depends on formats, standards, export paths, and enough internal knowledge to make an informed choice.
  • Keep Personal Data Controls NarrowExit planning also needs privacy-safe operations when data comes from third parties, stale contact records, or suppression workflows.

Study first

Review the ideas behind the questions

Review how to judge a martech choice before a useful shortcut becomes a hard dependency. Focus on exit evidence, open formats, supplier data proof, and the minimum personal data a workflow needs.

Balance Speed Against Exit Risk

A fast tool choice may still be reasonable, but advanced operations work makes the switching cost visible before the team commits.

  • Lock-in means switching from one technology or provider becomes difficult, time consuming, and disproportionately expensive.
  • Some lock-in can be worth accepting when the benefit outweighs the future switching cost.
  • Business cases should estimate the cost and time needed to exit provider arrangements.

In Practice

Do Not Treat Lock-In As One Word

Separate the value of the native feature from the cost, timing, data, and skill risk of leaving later.

Review After The Deal Is Signed

A provider can remain the right choice, but value and alternatives should still be reviewed as the stack changes.

Common mistakes

  • Approving a proprietary data move because the first launch will be faster.

    Estimate exit time and cost, then decide whether the speed benefit is worth the dependency.

Q&A

Is every lock-in risk a reason to reject a tool?

No. Compare the operating value with the future switching cost, data impact, and migration effort.

What evidence should an exit review include?

It should estimate switching time, exit cost, data movement, and whether the current benefit still justifies the dependency.

Protect Data Portability

Data control depends on formats, standards, export paths, and enough internal knowledge to make an informed choice.

  • SaaS decisions should prefer open standards and formats when data may need to move later.
  • Open standards support interoperability, data exchange, and independence from individual suppliers.
  • Technology choices should work with existing systems and adapt to future demands.

In Practice

Export Tests Beat Assumptions

If a vendor says data is portable, test whether another system can read the export before the workflow depends on it.

Skills Can Create Dependency

A team may choose one provider by default because that is where knowledge is concentrated, so broaden the review before making it policy.

Common mistakes

  • Calling a supplier-controlled format an open standard because the supplier shares it.

    Check whether the standard has transparent process, public documentation, collaboration, and market support.

Q&A

What makes a format safer for future migration?

Open, well-documented, broadly supported formats make data easier to move between systems.

Why can team expertise increase lock-in?

If only one provider is well understood, teams may keep choosing it for convenience instead of evaluating the best fit.

Keep Personal Data Controls Narrow

Exit planning also needs privacy-safe operations when data comes from third parties, stale contact records, or suppression workflows.

  • A buyer cannot rely only on a third party's assurance that marketing data is compliant.
  • Personal data should be adequate, relevant, and limited to what is necessary for the stated purpose.
  • A minimal suppression record can prevent future marketing to people who objected without keeping more data than needed.

In Practice

Supplier Evidence Comes First

Before enrichment or outreach, confirm where the data came from, what people were told, what consent exists, and how objections move between parties.

Accuracy Does Not Justify Tracing

A stale email address should not become a reason to append new broker data for marketing without the person's choice.

Common mistakes

  • Deleting objectors completely and losing the ability to screen future rented lists.

    Keep only the minimum clearly marked suppression data needed to respect the objection later.

Q&A

What should happen before using a rented marketing file?

Check source, privacy notice, consent evidence, suppression checks, rights handling, and whether the supplier evidence is reliable.

How narrow should suppression data be?

Keep enough to prevent future marketing mistakes, but no more than is needed for that suppression purpose.

Question quality

Reviewed before publishing

Reviewed by
Aniruddh Sharma
Last checked
August 22, 2026

Reviewed against current GOV.UK lock-in, open-standards, and Technology Code guidance plus ICO direct-marketing and minimisation guidance. These sources fit because the quiz tests platform-neutral martech dependency, data-control, supplier-evidence, and personal-data boundaries.

The source pages for this edition were checked as part of the same review. Official product docs are linked where available.

Sources

Sources used for this quiz

These pages support the quiz content and study notes.