Criar modelos de ML com o BigQuery ML: laboratório com desafio avaliações

Mahesh M. · Revisado há 1 day

anugrah S. · Revisado há 2 days

Sergii M. · Revisado há 2 days

Clauderson B. · Revisado há 2 days

zumlath s. · Revisado há 2 days

NIKHIL R. · Revisado há 2 days

Abhishek G. · Revisado há 2 days

Arijit G. · Revisado há 2 days

manaswin s. · Revisado há 2 days

good

Zaki Bimo N. · Revisado há 2 days

Jeni J. · Revisado há 2 days

Setp to evaluate an improved model is failing always

Mahesh M. · Revisado há 2 days

Sushant B. · Revisado há 2 days

thanks

Bagus A. · Revisado há 2 days

Kiran R. · Revisado há 2 days

good lab

Jit O. · Revisado há 2 days

Sheikh E. · Revisado há 2 days

Mahesh M. · Revisado há 2 days

Rohit P. · Revisado há 2 days

Brayen C. · Revisado há 2 days

Sarwaarth C. · Revisado há 2 days

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. · Revisado há 2 days

Aldi S. · Revisado há 2 days

dinda l. · Revisado há 2 days

Abhishek R. · Revisado há 2 days