Module quiz

1. Batch ingestion sends data to the data lake first, while streaming ingestion sends data to the profile store and data lake in parallel.
2. Batch ingestion updates profiles every 5 minutes, while streaming ingestion updates profiles every 30 minutes.
3. Streaming ingestion requires manual file uploads, while batch ingestion uses APIs exclusively.
4. Batch ingestion is used for real-time data, while streaming ingestion is used for historical data.

1. Field groups are used to store customer consent information.
2. Field groups allow for the nesting of related fields to create consistency across schemas.
3. Field groups are used to define marketing actions for data governance.
4. Field groups organize data and enable reuse across multiple schemas.

1. Data governance policies automatically delete outdated data.
2. Labels and marketing actions are linked through policies to enforce data governance.
3. Data governance policies are only applicable to batch ingestion workflows.
4. Labels are applied to customer profiles, while marketing actions are applied to schemas.

1. Query Service is used to create dashboards for visualizing data.
2. Query Service is used to automate data ingestion workflows.
3. Query Service allows users to run SQL queries on the data lake for ad hoc analysis and data validation.
4. Query Service is used to manage customer privacy requests.

1. Schemas cannot include nested fields.
2. Schemas define identities, which are used to build customer profiles and relationships between schemas.
3. Schemas are only used for batch ingestion workflows.
4. Schemas are automatically generated and cannot be customized.