What are benefits of using Adobe RT-CDP's NoSQL data model for customer data? (Select two.)

Question

Options

• AEfficient handling of unstructured data.
• BReal-time querying and processing capabilities.
• CAutomatic normalization of data into relational structures.
• DPredefined relationships between all datasets.

• A
  71% (39)
• C
  9% (5)
• D
  20% (11)

Explanation

Adobe RT-CDP uses a NoSQL data model precisely because customer data is inherently unstructured and varied - think clickstreams, behavioral events, and profile attributes that don't fit neatly into rows and columns. This makes A correct: NoSQL excels at storing and retrieving unstructured or semi-structured data without requiring a fixed schema. B is correct because NoSQL architectures (especially document and key-value stores) are optimized for low-latency reads and writes, enabling the real-time profile lookups and event processing that RT-CDP is built around.

C is wrong because automatic normalization into relational structures is the opposite of what NoSQL does - that's a hallmark of relational (SQL) databases, and normalization would actually slow down the flexible, schema-less approach RT-CDP needs. D is wrong because predefined relationships between all datasets describe a rigid relational model; NoSQL deliberately avoids enforcing such constraints to allow flexible data ingestion from diverse sources.

Memory tip: Think "NoSQL = No Schema, No Problem." The two benefits that survive without a schema are handling unstructured data (A) and speed at scale (B) - both of which relational databases sacrifice for structure and consistency.

No community discussion yet for this question.