A data analytics team is ingesting e-commerce transaction records from Cloud Storage into BigQuery. Each transaction record contains complex hierarchical information, including nested customer contact details and a repeated list of purchased product line items. Which file format should the team use to load this data while natively preserving its nested and repeated data structure?

Newline-delimited JSON (JSON Lines): ### **What Newline-delimited JSON is** **Newline-delimited JSON** (often referred to as **ndjson** or **JSON Lines**) is a semi-structured, text-based data interchange format where each individual line in a file contains a complete, valid **JSON object**. In data analytics and ingestion platforms like **BigQuery**, newline-delimited JSON is the standard JSON format used for batch data loads and streaming ingestion because each record is self-contained and separated by a newline character (`\n`). ### **How it meets the requirements:** - **Nested records support (✓):** JSON objects natively support key-value pairs where the value can be another JSON object. In BigQuery, these map directly to **STRUCT** (RECORD) data types, allowing complex sub-entities like customer contact profiles to remain grouped within the parent record. - **Repeated fields support (✓):** JSON natively supports arrays (e.g., `"items": [...]`), which BigQuery represents as **REPEATED** (ARRAY) fields. This allows multiple purchased items to be stored directly inside a single transaction record without requiring denormalization or separate child tables. - **Direct ingestion from Cloud Storage (✓):** BigQuery natively supports loading newline-delimited JSON files directly from **Cloud Storage** buckets into managed analytical tables. ### **Key advantages:** - **Flexible and self-describing:** JSON encodes attribute names alongside values, making it easier to represent evolving data structures and variable schemas. - **Hierarchical data representation:** Eliminates the immediate need for complex relational multi-table database joins when querying parent-child relationships. - **Standard cloud interchange format:** Highly compatible with web APIs, logging services, and distributed stream processing engines across Google Cloud. - **Parallel processing friendly:** Because each record occupies exactly one line, distributed ingestion systems can split large files efficiently along line boundaries. ### **Why this is optimal:** Unlike flat, tabular formats such as CSV that only represent two-dimensional rows and columns, **newline-delimited JSON** allows complex, multi-tiered business objects to be ingested into BigQuery in their natural structure. This avoids the overhead of flattening arrays or maintaining multiple related tables, making it the ideal choice for hierarchical transaction logs.

Newline Delimited Json Vs Csv Bigquery | Unlock the power of your data in the cloud! Get hands-on with Google Cloud's core data services like BigQuery and Looker to validate your practical skills in data ingestion, analysis, and management, and earn your Associate Data Practitioner certification!

FundamentalAssociate Data Practitioner

A data engineering team is designing a data ingestion and storage pipeline in Google Cloud. The architecture must support two primary use cases: Use Case 1: High-throughput streaming ingestion of individual, write-heavy event records where messages require schema evolution and fast row-level serialization. Use Case 2: Large-scale analytical processing where business intelligence queries scan and aggregate only 3 to 4 specific columns across billions of historical records. Which combination of data formats best aligns with the architectural requirements of these two use cases?

Distinguish the format of the data (e.g., CSV, JSON, Apache Parquet, Apache Avro, structured database tables)

FundamentalAssociate Data Practitioner

A data analytics team is preparing to ingest historical transaction data stored in Cloud Storage into BigQuery. The team requires an open-source, columnar storage format that is natively supported for automated data loading using the BigQuery Data Transfer Service. Which file format should the team use?

Distinguish the format of the data (e.g., CSV, JSON, Apache Parquet, Apache Avro, structured database tables)

FundamentalAssociate Data Practitioner

A data engineering team wants to automate an event-driven data processing pipeline on Google Cloud. When specific events occur in Google Cloud services, an event notification in the standardized CloudEvents format must immediately invoke a data transformation service deployed on Cloud Run. To ensure secure execution and proper event routing, what should the team configure?

Use Eventarc triggers in event-driven pipelines (Dataform, Dataflow, Cloud Functions, Cloud Run, Cloud Composer)

FundamentalAssociate Data Practitioner

A data analytics team is designing a data ingestion pipeline on Google Cloud. The team has established the following operational requirements: Raw transaction records from Cloud Storage must be ingested directly into BigQuery staging tables without prior processing. Data cleansing, standardization, and complex business metric aggregations must be performed directly within BigQuery using scheduled SQL queries. Data analysts must have continuous access to the original, unmodified raw datasets stored within the warehouse for exploratory queries. Which data pipeline methodology does this architecture represent?

FundamentalAssociate Data Practitioner

A data analytics team is designing a transformation pipeline to process large volumes of unstructured image data. The pipeline requires intensive linear algebra and numeric matrix computations for feature extraction before the processed metrics are loaded into BigQuery. The team needs a processing engine that supports specialized hardware acceleration (GPUs) to maximize execution performance. Which Google Cloud product should the team choose to implement this transformation pipeline?

AdvancedProfessional Cloud Data Engineer

An enterprise is designing a compute capacity strategy for its analytical workloads in BigQuery. The workload environment consists of three distinct patterns: Production ELT pipelines: Run continuously 24/7 with a predictable, steady baseline compute demand. Data science ad-hoc analytics: Intermittent, bursty compute usage during business hours that requires rapid scaling without manual intervention. Departmental BI dashboards: Variable query volume throughout the day that can tolerate shared capacity and should utilize spare resources when available. You need to optimize compute costs, prevent resource contention between workloads, ensure predictable performance, and maximize resource utilization across the organization. Which capacity management and reservation strategy should you implement?

Associate Data Practitioner

Newline Delimited Json Vs Csv Bigquery

Related questions