리뷰 BigQuery ML로 ML 모델 만들기: 챌린지 실습개

Clauderson B. · 2일 전에 리뷰됨

zumlath s. · 2일 전에 리뷰됨

NIKHIL R. · 2일 전에 리뷰됨

Abhishek G. · 2일 전에 리뷰됨

Arijit G. · 2일 전에 리뷰됨

manaswin s. · 2일 전에 리뷰됨

good

Zaki Bimo N. · 2일 전에 리뷰됨

Jeni J. · 2일 전에 리뷰됨

Setp to evaluate an improved model is failing always

Mahesh M. · 2일 전에 리뷰됨

Sushant B. · 2일 전에 리뷰됨

thanks

Bagus A. · 2일 전에 리뷰됨

Kiran R. · 2일 전에 리뷰됨

good lab

Jit O. · 2일 전에 리뷰됨

Sheikh E. · 2일 전에 리뷰됨

Mahesh M. · 2일 전에 리뷰됨

Rohit P. · 2일 전에 리뷰됨

Brayen C. · 2일 전에 리뷰됨

Sarwaarth C. · 2일 전에 리뷰됨

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. · 2일 전에 리뷰됨

Aldi S. · 2일 전에 리뷰됨

dinda l. · 2일 전에 리뷰됨

Abhishek R. · 2일 전에 리뷰됨

Shanmuganathan E. · 2일 전에 리뷰됨

Shayan D. · 2일 전에 리뷰됨

Task 3 is broken, had to run the challenge twice.

Ahmad H. · 2일 전에 리뷰됨