You use Azure Data Lake Storage Gen2.
You need to ensure that workloads can use filter predicates and column projections to filter data at the time the data is read from disk.
Which two actions should you perform? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.
To ensure workloads can use filter predicates and column projections to filter data at the time it is read from disk in Azure Data Lake Storage Gen2, two actions are necessary. First, you need to register the query acceleration feature. This feature enables filtering predicates and column projections, which optimize data processing by retrieving only the required data, thus reducing network latency and compute costs. Second, you should create a storage policy that is scoped to a container prefix filter. This allows you to specify which files and directories in a container should be eligible for query acceleration, further optimizing query performance by focusing only on a subset of the data in the container.
E. Register the query acceleration feature. D. Create a storage policy that is scoped to a container prefix filter. To filter data at the time it is read from disk, you need to use the query acceleration feature of Azure Data Lake Storage Gen2. To enable this feature, you need to register the query acceleration feature in your Azure subscription. In addition, you can use storage policies scoped to a container prefix filter to specify which files and directories in a container should be eligible for query acceleration. This can be used to optimize the performance of the queries by only considering a subset of the data in the container.
Option A, reregistering the Azure Storage resource provider, and Option C, reregistering the Microsoft Data Lake Store resource provider, are not necessary to enable filter predicates and column projections in Azure Data Lake Storage Gen2. Option D, creating a storage policy that is scoped to a container prefix filter, is not a valid option as Azure Data Lake Storage Gen2 does not support storage policies scoped to container prefix filters.
It has, I think
D + E = correct
E. Register the query acceleration feature. D. Create a storage policy that is scoped to a container prefix filter.
D. Create a storage policy that is scoped to a container prefix filter. E. Register the query acceleration feature. D&E are correct
Its D & E https://learn.microsoft.com/en-us/azure/storage/blobs/data-lake-storage-query-acceleration
Ignore this chatgpt pointing to B& E
mod kindly remove both the replies, not relevant.
B. Create a storage policy that is scoped to a container. Azure Data Lake Storage Gen2 supports hierarchical namespaces and allows you to define storage policies at various levels, including at the container level. E. Register the query acceleration feature. Azure Data Lake Storage Gen2 provides a feature called query acceleration, which optimizes query performance by using indexes and metadata caching. D is not an option because while you can create storage policies scoped to containers or paths within containers, creating a policy scoped to a container prefix filter specifically is not a standard option or action related to optimizing filter predicates and column projections in Azure Data Lake Storage Gen2.
Correction - Chatgpt : DE Option A, which suggests re-registering the Azure Storage resource provider, is typically not related to performance tuning or enabling specific features like query acceleration within a storage solution. Re-registering a resource provider is an administrative task that may be necessary when there are issues with the Azure subscription or the resource provider itself, which could affect the provisioning and management of Azure services. For the scenario described, where the goal is to filter data at the time it is read from disk to optimize query performance, re-registering the Azure Storage resource provider would not directly impact the ability to use filter predicates and column projections. Instead, enabling features that allow for such optimizations, like query acceleration (E), and setting up policies for how data is stored and accessed (D), are the relevant actions to take.
Chatgpt : AE Option A, which suggests re-registering the Azure Storage resource provider, is typically not related to performance tuning or enabling specific features like query acceleration within a storage solution. Re-registering a resource provider is an administrative task that may be necessary when there are issues with the Azure subscription or the resource provider itself, which could affect the provisioning and management of Azure services. For the scenario described, where the goal is to filter data at the time it is read from disk to optimize query performance, re-registering the Azure Storage resource provider would not directly impact the ability to use filter predicates and column projections. Instead, enabling features that allow for such optimizations, like query acceleration (E), and setting up policies for how data is stored and accessed (D), are the relevant actions to take.
should be correct
go to BE