---
title: "Discussion on \"Enrich Metadata and Discovery of Lakehouse Data: Challenge Lab - ARC123\" | Hashnode"
description: "Discussion on \"Enrich Metadata and Discovery of Lakehouse Data: Challenge Lab - ARC123\". In a challenge lab you’re given a scenario and a set of tasks. Instead of following step-by-step instructions, you will use the skills learned from the labs in the course to figure out how to complete the tasks on your own! An automated scoring system (shown on this page) will provide feedback on whether you have completed your tasks correctly."
url: "https://hashnode.com/posts/enrich-metadata-and-discovery-of-lakehouse-data-challenge-lab-arc123/6a7311950c2c828d6c16bb0d"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Enrich Metadata and Discovery of Lakehouse Data: Challenge Lab - ARC123](https://eplus.dev/enrich-metadata-and-discovery-of-lakehouse-data-challenge-lab-arc123?utm_source=hashnode&utm_medium=feed)

In a challenge lab you’re given a scenario and a set of tasks. Instead of following step-by-step instructions, you will use the skills learned from the labs in the course to figure out how to complete the tasks on your own! An automated scoring system (shown on this page) will provide feedback on whether you have completed your tasks correctly.

Aug 5 · 4 min read · eplus.dev  
Read the article

-   [#enrich-metadata-and-discovery-of-lakehouse-data-challenge-lab-arc123](https://hashnode.com/tag/enrich-metadata-and-discovery-of-lakehouse-data-challenge-lab-arc123)
-   [#enrich-metadata-and-discovery-of-lakehouse-data-challenge-lab](https://hashnode.com/tag/enrich-metadata-and-discovery-of-lakehouse-data-challenge-lab)
-   [#arc123](https://hashnode.com/tag/arc123)

## Written by

[David Nguyen](https://hashnode.com/@hoangit)

@hoangit · Ho Chi Minh, Vietnam

  
[View profile](https://hashnode.com/@hoangit)

hoangit

A passionate full-stack developer from @ePlus.DEV

## Responses 1

Markdown supported · ⌘↵ to post

[Ahmet Özel](https://hashnode.com/@ahmetozel)

[Aug 5](https://hashnode.com/posts/enrich-metadata-and-discovery-of-lakehouse-data-challenge-lab-arc123/6a7311950c2c828d6c16bb0d/comment/6a73730609f48592bb18a540)

The aspect improves discovery, but it is descriptive metadata rather than an access-control boundary. In a production version I would classify sensitive columns, attach policy tags or masking rules at the column level, and grant the connection service account only the storage permissions required for this object prefix. It is also worth testing that a user who can discover the table cannot query protected fields. That separates successful catalog enrichment from actual data protection.
