Courseiva

SC-900 Practice Question: Describe the concepts of security, compliance, and identity

Your company is implementing data loss prevention (DLP) policies in Microsoft Purview. You need to prevent users from sharing credit card numbers via email. Which type of sensitive information type should you use in the DLP rule?

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

Built-in sensitive information type

A built-in sensitive information type for credit card numbers is available in Microsoft Purview. Option A is incorrect because a custom keyword list would be inefficient and unreliable for detecting credit card numbers. Option C is incorrect because a trainable classifier is used for custom classification, not for predefined patterns like credit cards. Option D is incorrect because Exact Data Match (EDM) classification requires a custom database, not a built-in type.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Custom keyword list

    Why it's wrong here

    A custom keyword list would require manually listing all possible credit card number patterns, which is impractical. Built-in types already include regex and checksum validation.

  • Built-in sensitive information type

    Why this is correct

    Correct because Microsoft Purview includes a predefined sensitive information type for credit card numbers that uses pattern recognition, checksum validation, and keyword lists.

  • Trainable classifier

    Why it's wrong here

    Trainable classifiers are used for custom classification based on examples (e.g., contracts) but not for patterns like credit card numbers that are well-defined.

  • Exact data match (EDM) based classification

    Why it's wrong here

    Exact data match (EDM) based classification requires you to upload a custom database of specific values (e.g., a spreadsheet of actual credit card numbers) and then hash those values for matching. The scenario asks for a rule that prevents sharing *any* credit card number, not just a pre‑defined list of known numbers. EDM is tempting because it offers high‑precision detection for sensitive data you have already inventoried, such as employee payroll records, but it cannot detect patterns it has never seen, making it the wrong choice for a generic credit card number pattern.

About these practice questions

This SC-900 question is part of Courseiva's 1,250-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 →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This SC-900 practice question is part of Courseiva's free Microsoft 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 SC-900 exam.