Looker and Looker Studio are two different products with the word Looker in their names, and the Associate Cloud Engineer exam expects you to know the difference. This article covers what each one is, who actually uses them, and which one shows up on the ACE exam.
It does not cover the deep details of LookML, Looker's semantic modeling language, or the full feature catalog of either product. That is more relevant for a BI engineer than for the ACE exam.
Looker Studio is a free data visualization tool for creating dashboards and reports. It used to be called Google Data Studio and got renamed when Google folded it into the Looker brand. The product itself did not change much.
You connect it to a data source (BigQuery is the most common in GCP), drag charts onto a canvas, and build interactive dashboards. It is web-based, free, and easy to share. You can hand someone a link and they can view the dashboard in a browser.
For most use cases on the Associate Cloud Engineer exam, Looker Studio is the answer. If a scenario asks "we have data in BigQuery, we want to visualize it for stakeholders", Looker Studio fits.
Looker is a paid enterprise BI platform with a semantic modeling layer (LookML) that lets a data team define metrics and dimensions once and have everyone in the company use those consistent definitions.
The semantic layer is the actual differentiator. In Looker Studio, every dashboard creator writes their own query or pulls from raw tables. In Looker, a data engineer defines what "monthly recurring revenue" means in LookML, and every dashboard, report, and embedded visualization in the company uses that definition. That consistency is what enterprise BI tools sell, and it is why Looker is expensive.
Looker Studio is for dashboards. You want a chart, you build a chart. Anyone with a Google account can use it.
Looker is for being the BI system of record. A data team builds the LookML model, business users explore data through that model, and the model enforces consistent definitions across the organization. It also supports embedded analytics and custom application development on top of that model.
If a company has five people who each want to make a dashboard for their own slice of data, Looker Studio is the right answer. If a company has 500 people across departments who all need to see the same metrics defined the same way, Looker is the right answer (and they are paying for it accordingly).
The Associate Cloud Engineer exam says it directly. Looker is unlikely to show up on the exam. Looker Studio is what you need to know.
The exam pattern is consistent. A scenario describes a team with data in BigQuery (or another GCP source) that needs to build dashboards or reports for stakeholders. The right answer is Looker Studio. Wrong answers usually involve building a custom application or exporting data to a third-party tool.
If a scenario specifically calls for "enterprise BI with a semantic model", "consistent metric definitions across the organization", or "embedded analytics in a customer-facing application", that is when Looker (the paid product) becomes the right answer. Those scenarios are rarer on the ACE exam.
The naming is genuinely confusing. Both products are called Looker something. Both visualize data. Both can connect to BigQuery. The difference is one is free and dashboard-focused, the other is a paid enterprise BI platform.
If you see "Looker Studio" in a question, it is the free tool. If you see just "Looker", it is the enterprise product. They are not the same thing and the exam will not use the names interchangeably.
If you see "free", "dashboard", "report", "visualize BigQuery data", think Looker Studio. If you see "semantic layer", "LookML", "enterprise BI", or "embedded analytics", think Looker.
Looker Studio is the free dashboarding tool, formerly Data Studio. Looker is the paid enterprise BI platform with a semantic modeling layer. They share a brand and not much else. The Associate Cloud Engineer exam mostly tests Looker Studio, because that is the tool teams reach for when they have BigQuery data and need to build dashboards. Looker shows up rarely, and when it does, the scenario is almost always about a semantic layer or enterprise BI requirements that Looker Studio cannot meet.
My Associate Cloud Engineer course covers Looker Studio in the BigQuery and visualization section, including how it integrates directly with BigQuery query results and how it shows up on the ACE exam.
