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?

⚠ Common exam trap

The trap is over-engineering the answer — candidates may pick EDM or trainable classifiers thinking 'more advanced equals better,' when the exam expects recognition that a built-in SIT already covers standard credit card detection.

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

Microsoft Purview ships with built-in sensitive information types (SITs) that already detect credit card numbers using validated patterns, including the Luhn checksum and contextual keywords like 'credit card' or 'CVV.' Using the built-in 'Credit Card Number' SIT is the fastest, most accurate way to enforce a DLP rule blocking card numbers in email. Custom or EDM approaches are unnecessary when a ready-made SIT exists.

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 matches literal terms an administrator enters, so it cannot detect the numeric patterns and checksum structure of card numbers. It is tempting for organisation-specific identifiers, but the built-in Credit Card Number sensitive information type performs the pattern and validation checks required.

  • ✓

    Built-in sensitive information type

    Why this is correct

    A built-in sensitive information type detects predefined patterns such as credit card numbers using validated checksums and keywords, so the DLP rule can block email sharing without custom regex authoring. It directly satisfies the requirement to prevent credit card numbers leaving via email.

  • ✗

    Trainable classifier

    Why it's wrong here

    Trainable classifiers learn from labelled example content and suit subjective categories such as resumes or source code, not fixed-format numeric patterns. It is tempting because they detect sensitive material without predefined patterns, but credit card numbers need the built-in Credit Card Number sensitive information type.

  • ✗

    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,279-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 and reviewed by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

Last reviewed September 2026 · checked against the official Microsoft exam blueprint

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.