A financial institution needs to ingest sensitive customer data, including credit card transactions, while ensuring real-time updates to customer profiles. What considerations should they prioritize?

Question

Options

• AEnable Edge ingestion with encryption for sensitive data.
• BRely solely on batch ingestion workflows.
• CDisable real-time updates to ensure data consistency.
• DAvoid using streaming connectors for sensitive data.

• A
  77% (24)
• B
  6% (2)
• C
  3% (1)
• D
  13% (4)

Explanation

Option A is correct because financial institutions handling sensitive data like credit card transactions must combine low-latency ingestion (Edge ingestion brings processing closer to the data source) with encryption to protect data in transit and at rest - satisfying both the real-time and security requirements simultaneously.

Why the distractors are wrong:

• B (batch ingestion only) directly contradicts the requirement for real-time profile updates; batch jobs run on schedules, not continuously.
• C (disable real-time updates) eliminates the core business requirement - real-time fraud detection and profile accuracy depend on live updates.
• D (avoid streaming connectors) is backwards; streaming is necessary for real-time ingestion - the concern should be securing the stream, not eliminating it.

Memory tip: Think "Encrypt, don't eliminate." When exam questions pair sensitive data with real-time requirements, the answer will always secure the real-time pipeline rather than remove it. "Edge + encryption" is the pattern for low-latency, high-security ingestion scenarios.

No community discussion yet for this question.