What is the key difference between RDBMS and Adobe RT-CDP's NoSQL data model?

Question

Options

• ART-CDP's NoSQL model supports only structured data.
• BRT-CDP's NoSQL model uses schema-on-write instead of schema-on-read.
• CRT-CDP's NoSQL model is designed to store hierarchical and unstructured data efficiently.
• DRT-CDP's NoSQL model requires predefined relationships between tables.

• A
  6% (4)
• B
  10% (7)
• C
  70% (49)
• D
  14% (10)

Explanation

Option C is correct because RT-CDP (Real-Time Customer Data Platform) is built on a NoSQL foundation - specifically Adobe Experience Platform's data lake - which is optimized for storing hierarchical data structures (like nested JSON profiles) and unstructured/semi-structured data such as behavioral events, clickstreams, and raw ingestion payloads. Traditional RDBMS enforces rigid tabular structures with predefined schemas, making it poorly suited for this variety of data.

Why the distractors are wrong:

• A is the opposite of reality - NoSQL's key advantage over RDBMS is handling unstructured and semi-structured data, not limiting to structured data only.
• B reverses the concepts: RDBMS typically enforces schema-on-write (structure defined before data is stored), while NoSQL/data lake approaches favor schema-on-read (structure interpreted at query time). RT-CDP follows schema-on-read.
• D describes RDBMS behavior - predefined foreign keys and join relationships are a hallmark of relational databases, not NoSQL systems, which deliberately avoid mandatory relationship constraints.

Memory tip: Think of RT-CDP as a "flexible profile container" - it needs to absorb messy real-world data from hundreds of sources (web, mobile, CRM, offline) without forcing everything into rigid rows and columns first. That flexibility = NoSQL + hierarchical/unstructured storage.

No community discussion yet for this question.