One of your query is taking a long time to finish, when you open the query profiler you see that lot of data is spilling to the remote disk(Bytes spilled to remote storage).
What may be the cause of this?
A . The amount of memory available for the servers used to execute the operation might not be sufficient to hold intermediate results
B. The size of the AWS bucket used to hold the data is not sufficient for the query
C. Number of disks attached to the virtual warehouse is not enough for the processing
Answer: A
Explanation:
This is again a question based on work experience. One variation of this may be, you will be given a
query profile snapshot which will be having a huge number against Bytes spilled to remote storage. You
will be asked to find the possible cuase
Queries Too Large to Fit in Memory
For some operations (e.g. duplicate elimination for a huge data set), the amount of memory available for the servers used to execute the operation might not be sufficient to hold intermediate results. As a result, the query processing engine will start spilling the data to local disk. If the local disk space is not sufficient, the spilled data is then saved to remote disks.
This spilling can have a profound effect on query performance (especially if remote disk is used for spilling). To alleviate this, we recommend:
Latest ARA-C01 Dumps Valid Version with 156 Q&As
Latest And Valid Q&A | Instant Download | Once Fail, Full Refund