Data Fusion for ETL in GCP - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a new Data Fusion instance in GCP.

GCP

gcloud datafusion instances create [1] --location=us-central1 --type=BASIC

Drag options to blanks, or click blank then click option'

Acreate-instance

Bmy-instance

Cdatafusion1

Dinstance123

Attempts:

3 left

💡 Hint

Common Mistakes

Using a command keyword instead of an instance name.

Including spaces or special characters in the instance name.

The command requires the instance name as the first argument. 'my-instance' is a valid name.

2fill in blank

medium

Complete the code to start a pipeline run in Data Fusion.

GCP

gcloud datafusion pipelines run [1] etl-pipeline --location=us-central1

Drag options to blanks, or click blank then click option'

Adefault-instance

Bpipeline-runner

Cfusion-instance

Dmy-instance

Attempts:

3 left

💡 Hint

Common Mistakes

Using a generic or incorrect instance name.

Confusing pipeline name with instance name.

The instance name must match the Data Fusion instance where the pipeline is deployed. 'my-instance' is correct here.

3fill in blank

hard

Fix the error in the pipeline configuration to specify the source plugin correctly.

GCP

"source": {"name": "[1]", "type": "plugin"}

Drag options to blanks, or click blank then click option'

ABigQuerySource

BBigQuerySink

CGCSFile

DPubSubSource

Attempts:

3 left

💡 Hint

Common Mistakes

Using a sink plugin name for the source.

Confusing GCS or Pub/Sub plugins with BigQuery.

The source plugin for reading from BigQuery is 'BigQuerySource'. 'BigQuerySink' is for writing data.

4fill in blank

hard

Fill both blanks to filter records where the 'age' field is greater than 30 in the Wrangler transform.

GCP

"filterCondition": "[1] [2] 30"

Drag options to blanks, or click blank then click option'

Aage

B>

C<

Dage >

Attempts:

3 left

💡 Hint

Common Mistakes

Using '<' instead of '>'.

Combining field and operator in one blank.

The filter condition requires the field name 'age' followed by the greater than operator '>'.

5fill in blank

hard

Fill all three blanks to define a pipeline schedule that runs daily at midnight.

GCP

"schedule": {"type": "[1]", "startTime": "[2]", "interval": "[3]"}

Drag options to blanks, or click blank then click option'

Atime-based

B00:00

C24h

Devent-based

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'event-based' instead of 'time-based'.

Incorrect time format for startTime.

Wrong interval value for daily schedule.

The schedule type for time-based runs is 'time-based'. The start time at midnight is '00:00', and the interval for daily runs is '24h'.