Prepstellar

DP-700 · Practice set 16 of 17

OneLake Row, Column, and Folder Security: 10 practice questions

10 questions · Untimed · Free

10 free DP-700 practice questions on OneLake Row, Column, and Folder Security, with an explanation for every answer. Untimed. The full mock exam and the timed version are in the app.

Set 16 · OneLake Row, Column, and Folder Security · 10 questions Read the lesson
  1. Question 1 of 10

    A role hides two columns of a table. A member runs `SELECT *` on the table in a Spark notebook and gets a result. The same member runs the same query in the SQL analytics endpoint. What happens there?

    1. AThe query returns only the allowed columns
    2. BThe query returns the hidden columns filled with nulls
    3. CThe query succeeds, and the hidden columns show their names only
    4. DThe query returns an error
    Show the answer

    A request for every column includes columns the user may not read, and each engine handles it in its own way. Spark notebooks leave out the hidden columns and succeed. The SQL analytics endpoint and semantic models refuse the query with an error.

    Next → 1 / 10
  2. Question 2 of 10

    After a table change, a row rule in a OneLake security role references a column that is no longer in the table. What do members of the role get when they query the table?

    1. AThe rule is skipped and all rows are returned
    2. BThe last result that was valid is returned from a cache
    3. CThe missing column is added with null values
    4. DThe query fails and returns no data
    Show the answer

    Rules fail closed. When a row or column rule does not match its table, for example because it references a column that is not there, the query fails. A broken rule never opens the table.

    Next → 2 / 10
  3. Question 3 of 10

    The same group of users must see only the rows of their region in a Delta Parquet table and must not see its Salary column. How should the two rules be placed so that queries work?

    1. AThe row rule in one role, the column rule in a second
    2. BThe column rule in a Read role and the row rule in a ReadWrite role
    3. CThe row rule and the column rule in one OneLake security role
    4. DThe row rule in a role and a folder grant that leaves out Salary
    Show the answer

    Rules that must apply together go in the same role, because OneLake resolves each role alone and then adds the roles up. Row-level and column-level security on one table are supported when a single role holds both.

    Next → 3 / 10
  4. Question 4 of 10

    In a lakehouse, the folder `Files/Raw` contains the folder `Sales`, the folder `HR`, and the file `budget.csv`. A role grants Read on `Files/Raw/Sales` and on nothing else. What can a member of the role do?

    1. ARead the files directly in `Sales`, but not the subfolders that `Sales` contains
    2. BRead everything under `Raw`, because a grant on a folder extends to its parent
    3. CRead nothing, until a second role also grants Read on `Raw` and on `Files`
    4. DRead everything under `Sales` and traverse `Raw`, without seeing `HR` or `budget.csv`
    Show the answer

    A folder grant moves in two directions. Down, it inherits to the files and subfolders. Up, it gives traversal: the member can list and cross the parent folders to reach the grant, but siblings of the granted folder stay invisible.

    Next → 4 / 10
  5. Question 5 of 10

    A workspace Viewer belongs to Role1, which allows the columns Region and Revenue of the Sales table, and to Role2, which allows Region and Target. Neither role has row rules. The Viewer reads Sales in a Spark notebook and in the SQL analytics endpoint. Which columns can the Viewer read?

    1. AAll three columns in both, because roles combine as a union
    2. BAll three columns in Spark, and only Region in the endpoint
    3. COnly Region in both, because hidden columns work as a deny
    4. DOnly Region in Spark, and all three columns in the endpoint
    Show the answer

    Column lists of several roles combine as a union in general, so each role adds its columns. The SQL analytics endpoint is the exception: if any role hides a column, the endpoint blocks it, so the columns allowed by every role are the ones that remain.

    Next → 5 / 10
  6. Keep the ones you got wrong

    In the app, every question you miss comes back exactly when you’re about to forget it.

    Opens in your browser. Nothing to install.

    Start studying

    On your phone, with the same account

    Get it on Google Play Download on the App Store
  7. Question 6 of 10

    A lakehouse table has a row rule in a OneLake security role. A workspace Contributor who is a member of the role sees every row of the table in a Spark notebook, but fewer rows in the SQL analytics endpoint, which uses user identity mode. How should the team read this?

    1. AAs expected, because in this mode row rules are enforced for all users
    2. BAs a sync error, because roles never restrict a workspace Contributor
    3. CAs a SQL permission problem, because a `GRANT` on the table is missing
    4. DAs a caching delay, because the notebook will show fewer rows in an hour
    Show the answer

    OneLake security roles normally leave Admin, Member, and Contributor untouched, which explains the notebook. The exception is row-level security read through a SQL analytics endpoint in user identity mode: there the row rules are enforced for all users, including those three roles.

    Next → 6 / 10
  8. Question 7 of 10

    A workspace Viewer belongs to one OneLake security role, which grants the tables of the `sales` schema. In the object explorer of the SQL analytics endpoint, the Viewer also sees a schema named `hr`, with no tables in it. What explains this?

    1. AThe endpoint lists every schema name and hides only the unreadable tables
    2. BThe role is misconfigured, because a schema without a grant must stay hidden
    3. CTraversal opens `hr`, because it is a sibling of the granted schema
    4. DThe `hr` tables are still synchronizing and will appear after a short wait
    Show the answer

    Names and data follow different rules. The SQL analytics endpoint always returns all schema names, whatever the user's table permissions are, and it filters out the tables the user cannot read. An empty schema in the explorer is expected and is not a fault.

    Next → 7 / 10
  9. Question 8 of 10

    A Sales table has four rows: order 1 (Amount 50000, State CA), order 2 (Amount 72000, State CA), order 3 (Amount 90000, State WA), and order 4 (Amount 30000, State CA). A OneLake security role has the row rule `SELECT * FROM Sales WHERE Amount > 50000 AND State='CA'`. A workspace Viewer is in this role and in no other. Which orders does the Viewer see?

    1. AOrder 2 and no other
    2. BOrders 2 and 3
    3. COrders 1 and 2
    4. DOrders 1, 2, 3, and 4
    Show the answer

    Read the `WHERE` clause one condition at a time. `AND` needs both conditions to be true on the same row, and greater than leaves out the value itself. A visible row has an Amount above 50000 and also the State CA.

    Next → 8 / 10
  10. Question 9 of 10

    A OneLake security role allows the columns CustomerID, Name, and Country of the Customers table and hides the others. Viewers in the role query the table through a SQL analytics endpoint in user identity mode. An engineer renames Country to CountryCode in the table, and the Viewers lose all access to Customers. The new column name must stay. What restores their access?

    1. AWait for the security sync, which applies the new column name to the role
    2. BRename the column back to Country, so the allow list matches the table again
    3. CUpdate the column rule of the role, in the lakehouse where the role was created
    4. DRun `GRANT SELECT` on the CountryCode column for the Viewers at the endpoint
    Show the answer

    The allow list of a column rule is tied to column names. After a rename the rule is invalid and denies the whole table. The rule has to be corrected where it lives: in the role, in the lakehouse where the role was created.

    Next → 9 / 10
  11. Question 10 of 10

    A Delta Parquet table has a row rule in a OneLake security role. An engineer renames the table. What is the risk?

    1. AThe rule no longer applies to the table, and data can be exposed
    2. BThe rule follows the table, because roles are tied to its folder
    3. CThe table is blocked for all users until the old name is restored
    4. DThe rule moves to the new name with the next security sync
    Show the answer

    OneLake security roles are tied to the table name. A rename breaks the association, and nothing reapplies the rule for you. Until someone applies the policies again, the renamed table can show rows that the rule used to hide.

    Next → 10 / 10
  12. You’ve finished this set

    That’s 10 questions on OneLake Row, Column, and Folder Security. In the app the ones you miss come back exactly when you’re about to forget them.

    Back to the course Next lesson: Warehouse SQL Granular Security

    Opens in your browser. Nothing to install.

    Start studying

    On your phone, with the same account

    Get it on Google Play Download on the App Store

The whole course, on your computer and your phone

Lessons you can read, audio you can listen to on the way to work, and practice that remembers what you got wrong.

Opens in your browser. Nothing to install.

Start studying

On your phone, with the same account

Get it on Google Play Download on the App Store

“This app is the ‘One Lake’ for preparing the certification exams. Really worth it.”

Abdelhak Y. Google Play review