Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Associate Data Practitioner practice bank has 1,132 more like it. Try 10 free: instant score, no account.
A Looker developer is updating an e-commerce view file (order_items.view) to improve data discovery and report readability for business users. The team has outlined the following four requirements:
shipping_city, shipping_state, and shipping_zip) together inside a single collapsible drop-down folder within the view in the field picker.total_revenue measure so users see an explanatory definition when hovering over its information icon in the field picker.total_revenue measure in data tables and visualizations to appear as currency (for example, $1,250.00).usr_id to Customer ID without altering how the field is referenced in LookML models.Which group of LookML parameters should the developer apply to satisfy all four requirements?
fields for grouping dimensions into a drop-down list, description for contextual hover guidance, sql for currency display formatting, and group_item_label for the custom field display namefields: Operates at the Explore or Join level to specify which fields or sets are exposed to or excluded from the field picker.description: Correctly specifies tooltip information for dimensions and measures in the field picker and data tables.sql: Defines the raw SQL expression or underlying database column that generates the field's data value.group_item_label: Modifies the label of an individual field specifically when it is displayed underneath a group_label.fields parameter acts as a whitelist or blacklist to show or hide fields in an Explore; it cannot create drop-down folders within a view.sql parameter using SQL functions (such as CONCAT('$', ...) or TO_CHAR(...)) transforms the numeric measure into a string. This breaks visualization charting engines, aggregation calculations, and sorting in Looker.group_item_label does not serve as a general field rename for standalone dimensions like usr_id; it only affects fields already grouped under a group_label.sql for display formatting strips numeric properties, preventing Looker from treating values as plottable metrics.fields manages Explore visibility, not organizational grouping.group_item_label requires an active group_label to take effect.The objective were to restrict an Explore's exposed fields to a small list (fields) and shorten the visible names of dimensions that already reside inside an established group label (group_item_label).
group_label for grouping dimensions into a drop-down list, description for contextual hover guidance, value_format for currency display formatting, and label for the custom field display nameLookML offers several presentation-focused parameters designed to improve the end-user experience without altering the underlying data structures or LookML references:
group_label: Combines dimensions or measures into a collapsible drop-down list under a unified sub-heading within a view in the field picker.description: Defines explanatory text that appears when an end user hovers over the information icon next to a field name in the field picker or column headers in data tables.value_format: Applies Excel-style formatting strings to numeric fields to determine how data values render (such as currency or percentages) across tables and visualizations.label: Overrides the default display name of an individual field in the field picker without changing its underlying LookML field identifier.group_label: "Shipping Information" on shipping_city, shipping_state, and shipping_zip nests all three dimensions neatly inside an expandable accordion folder labeled Shipping Information inside the field picker.description: "Total gross revenue calculated before applying customer coupons." to total_revenue creates an info icon in the field picker that reveals this definition upon hover.value_format: "$#,##0.00" to the total_revenue measure formats numbers such as 1250 into standard United States currency ($1,250.00) across all queries and visualizations.label: "Customer ID" on the usr_id dimension changes its visual representation in the Explore field picker to Customer ID while keeping its reference name ${usr_id} intact for developers.This combination precisely targets field-level presentation and usability. It cleanly organizes the field picker, clarifies metrics through native tooltips, standardizes numeric outputs, and humanizes technical database column names—all through simple, declarative LookML parameters.
view_label for grouping dimensions into a drop-down list, note for contextual hover guidance, style for currency display formatting, and alias for the custom field display nameview_label: Changes the top-level view heading under which a field is grouped in the field picker, rather than nesting fields in an internal drop-down folder.note: Is not a valid LookML field parameter for generating field picker tooltip guidance; notes in Looker are used on dashboard tiles.style: Formats fields exclusively of type: tier (such as age brackets), determining whether tiers display in classic, interval, relational, or integer notation.alias: Declares legacy field names so that existing bookmarks and saved URLs containing old field identifiers continue to function when a field is renamed.view_label relocates fields under a separate major view header in the field picker instead of nesting them in a collapsible drop-down list within their parent view.note does not display an informational tooltip icon in the Explore field picker. The proper field-level parameter for this purpose is description.style parameter is reserved strictly for type: tier dimensions and cannot apply Excel-like currency formatting ($#,##0.00) to numeric measures.alias does not change the user-facing display label of a field in the field picker; it only provides alternative query aliases for URL routing and backward compatibility.view_label separates denormalized tables into apparent separate views rather than creating collapsible sub-folders.style supports values like classic or interval, but cannot accept currency format strings.alias works behind the scenes and does not alter UI labels.The goal were to split a wide denormalized table into distinct virtual views (view_label), preserve URL functionality for a previously renamed database column (alias), and format an age bracket tier dimension (style).
drill_fields for grouping dimensions into a drop-down list, label for contextual hover guidance, html for currency display formatting, and view_label for the custom field display namedrill_fields: Defines the list of detailed dimensions and measures that appear in an overlay modal when a user clicks an aggregated measure value in a visualization or table.label: Sets the visible display text for a field, view, or Explore in the Looker user interface.html: Injects custom HTML and Liquid styling into field output cells (such as font colors, conditional status badges, or embedded links).view_label: Overrides the top-level view heading for a field, causing it to appear grouped under a different view name.drill_fields manages click-through drill-down paths for granular analysis; it does not organize fields into collapsible folders in the field picker.label replaces the field's title in the field picker rather than adding explanatory hover text or info icon tooltips.html can customize the appearance of values using HTML formatting tags, it does not provide native numeric formatting for charts or visualization axes. Standard currency formatting is intended to be applied via value_format or value_format_name.view_label on usr_id moves the field to a different view section in the picker, rather than renaming the field itself to Customer ID.drill_fields governs analytical interaction workflows, not field picker layout.html changes cell markup but does not update underlying numeric axis scales or export formatting.label sets the name, while description provides the definition.The requirement called for enabling users to click into a metric to view underlying user attributes (drill_fields) and applying conditional color coding (such as green for positive values) using HTML and Liquid (html).
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated