You are an Azure Data Engineer. To accomplish your task, you need to design your table service solution to be read efficient. Which of the following are the possible guidelines/ recommendations that you would follow to make your solution to be read efficient?

Answer options:

A.Normalize the data as possible
B.Don’t create hot partitions
C.Use compound key values
D.Use Query projection
E.Specify either Rowkey or Partitionkey (not both) in the queries

Correct Answers: C and D 
Here are some guidelines for designing table service solution to be read-efficient: Design for querying in read-heavy applications
Specify both RowKey and PartitionKey in the queries
Embrace storing duplicate copies for entities
Embrace denormalizing your data
Use compound key values
Use query projection
Option A is incorrect. Read efficient solution advocates denormalizing the data, not normalizing as table storage is a cheap solution.
Option B is incorrect. Not creating hot partitions is a guideline to design your Table service solution to be write-efficient.
Option C is correct. Using compound key value is a recommended guideline for being the table service solution read -efficient.
Option D is correct. Using query projection is a recommended guideline for being the table service solution read -efficient. It enables reducing the amount of data that you transfer over the network with the help of queries selecting only the fields that are required.
Option E is incorrect. The recommended guideline to be the table service solution read efficient is to specify both RowKey and PartitionKey in the queries.
Reference: 
To know more about guidelines for table design, please visit the below-given link: 

https://docs.microsoft.com/en-us/azure/storage/tables/table-storage-design-guidelines