Opinie (Create ML Models with BigQuery ML: Challenge Lab)

Mahesh M. · Sprawdzono 1 dzień temu

anugrah S. · Sprawdzono 2 dni temu

Sergii M. · Sprawdzono 2 dni temu

Clauderson B. · Sprawdzono 2 dni temu

zumlath s. · Sprawdzono 2 dni temu

NIKHIL R. · Sprawdzono 2 dni temu

Abhishek G. · Sprawdzono 2 dni temu

Arijit G. · Sprawdzono 2 dni temu

manaswin s. · Sprawdzono 2 dni temu

good

Zaki Bimo N. · Sprawdzono 2 dni temu

Jeni J. · Sprawdzono 2 dni temu

Setp to evaluate an improved model is failing always

Mahesh M. · Sprawdzono 2 dni temu

Sushant B. · Sprawdzono 2 dni temu

thanks

Bagus A. · Sprawdzono 2 dni temu

Kiran R. · Sprawdzono 2 dni temu

good lab

Jit O. · Sprawdzono 2 dni temu

Sheikh E. · Sprawdzono 2 dni temu

Mahesh M. · Sprawdzono 2 dni temu

Rohit P. · Sprawdzono 2 dni temu

Brayen C. · Sprawdzono 2 dni temu

Sarwaarth C. · Sprawdzono 2 dni temu

The lab's core BQML syntax (CREATE MODEL, ML.PREDICT) is straightforward, but the surrounding task design has significant friction points that go beyond testing ML engineering skills: Undocumented domain knowledge required. The lab assumes prior familiarity with the Google Analytics BigQuery export schema — e.g. mapping hits.eCommerceAction.action_type numeric codes (0-8) to their meaning, or knowing that "traffic source" in the prompt actually maps to channelGrouping rather than the more intuitively-named trafficSource column. None of this is documented in the lab itself; it requires external research or prior GA360 experience.Mismatch with stated learning objective. This is positioned as an "ML Engineer" cert path (model deployment focus), but a large share of the lab's difficulty is data-analyst-level work: schema archaeology, e-commerce funnel semantics, and column disambiguation — not ML deployment itself. BQML's train/predict duplication isn't called out as a limitation. Feature engineering logic must be manually duplicated between the CREATE MODEL query and the ML.PREDICT query, with no pipeline abstraction (unlike sklearn/Vertex AI pipelines). This isn't explained anywhere in the lab, so a mismatch (e.g. missing a feature column) only surfaces as an opaque runtime error. Suggestion: Either provide a schema reference / glossary as part of the lab material, or explicitly frame this lab as also testing data exploration skills — not just ML deployment.

VINCENT L. · Sprawdzono 2 dni temu

Aldi S. · Sprawdzono 2 dni temu

dinda l. · Sprawdzono 2 dni temu

Abhishek R. · Sprawdzono 2 dni temu