What is a characteristic of the use of external tokenization?

Question

Options

• ASecure data sharing can be used with external tokenization.
• BExternal tokenization cannot be used with database replication.
• CPre-loading of unmasked data is supported with external tokenization.
• DExternal tokenization allows the preservation of analytical values after de-identification.

• B
  3% (1)
• C
  3% (1)
• D
  94% (34)

Explanation

External tokenization preserves analytical values after de-identification (D) because tokenization replaces sensitive data with format-consistent tokens that maintain the structural and relational properties of the original values. This means operations like grouping, counting, and trend analysis remain valid on tokenized data - unlike hashing or random masking, which destroy these properties.

Why the distractors are wrong:

• A is incorrect: Secure Data Sharing is not compatible with external tokenization policies - sharing across accounts does not support this feature.
• B is incorrect because it states the opposite of reality - external tokenization can be used with database replication, so the "cannot" makes this false.
• C is incorrect: Pre-loading of unmasked (plaintext) data is not supported with external tokenization; the external service handles detokenization at query time, not during data load.

Memory tip: Think of tokenization as a "format-preserving disguise" - the data looks the same shape and can still be analyzed, but the real values are hidden. That's what makes analytical preservation the defining characteristic that sets it apart from other de-identification methods.

No community discussion yet for this question.