Why data lake architecture centralizes data in Hadoop - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why does a data lake centralize data?

Which reason best explains why data lake architecture centralizes data?

A It stores all types of data in one place, making it easier to access and analyze.

B It separates data into many small silos to improve security.

C It only stores structured data to reduce storage costs.

D It duplicates data across multiple systems to increase speed.

💡 Hint

Think about how data lakes handle different data types and storage.

Data lakes centralize data by storing all types of data (structured, unstructured, semi-structured) in one place. This makes it easier to access and analyze diverse data sets.

🧠 Conceptual

intermediate

What is a key benefit of centralizing data in a data lake?

What is a main benefit of having centralized data in a data lake architecture?

A It requires data to be converted to a single format before storage.

B It enables unified data governance and security policies.

C It restricts data access to only one user at a time.

D It allows for faster data duplication across systems.

💡 Hint

Consider how centralization affects managing data rules and security.

Centralizing data in a data lake allows organizations to apply consistent governance and security policies across all data, improving control and compliance.

❓ data_output

advanced

Data lake stores multiple data types

Given a Hadoop data lake storing different data types, which output shows the correct count of each data type stored?

Hadoop

data = [
  {'type': 'structured', 'count': 1500},
  {'type': 'unstructured', 'count': 3000},
  {'type': 'semi-structured', 'count': 1200}
]

counts = {item['type']: item['count'] for item in data}
print(counts)

A {'structured': 1200, 'unstructured': 3000, 'semi-structured': 1500}

B {'structured': 1500, 'unstructured': 1200, 'semi-structured': 3000}

C {'structured': 1500, 'unstructured': 3000, 'semi-structured': 1200}

D {'structured': 3000, 'unstructured': 1500, 'semi-structured': 1200}

💡 Hint

Look carefully at the count values for each data type in the list.

The dictionary comprehension correctly maps each data type to its count as given in the list.

🧠 Conceptual

advanced

Why is schema-on-read important in data lakes?

Why does data lake architecture use schema-on-read instead of schema-on-write?

A It allows storing raw data without upfront formatting, enabling flexible analysis later.

B It forces data to be cleaned before storage, improving data quality immediately.

C It requires data to be converted to a fixed schema before saving, reducing errors.

D It duplicates data into multiple schemas for faster querying.

💡 Hint

Think about when the data structure is applied in schema-on-read.

Schema-on-read means data is stored raw and the structure is applied only when reading it, allowing more flexibility for different analysis needs.

🚀 Application

expert

Analyzing data lake centralization impact on Hadoop cluster

You have a Hadoop data lake storing all company data centrally. Which impact is most likely when centralizing data this way?

A Lower storage costs because data is duplicated across multiple clusters.

B Faster query speed because data is pre-aggregated before storage.

C Reduced data accessibility due to data being split across many nodes.

D Improved data accessibility but increased network traffic during large queries.

💡 Hint

Consider how centralizing data affects access and network use in Hadoop.

Centralizing data in a Hadoop data lake improves accessibility but can increase network traffic when querying large datasets across nodes.