If you don’t specify the command option ("checkpointLocation", pointer-to-checkpoint directory) in Structured Streaming, what will happen?

Answer options:

A.With the stoppage of the streaming job, all state data around the streaming job is lost and on the restart, the job must start from scratch.
B.With the stoppage of the streaming job, all state data around the streaming job is dumped to a default location and on the restart, the job must start from the aggregated data rather than tuned specific data.
C.It won’t be possible to create more than 1 streaming query that utilizes the same streaming source because of conflict issues.
D.The streaming job will function as expected because of the non-existence of the checkpointLocation option.

Correct Answer: A 
You need to set checkpointLocation for many sinks utilized in Structured Streaming. For the sinks where this setting is optional, if you don’t set this value, you are at risk of losing your place in the stream.
Option A is correct. If you don’t specify the command option ("checkpointLocation", pointer-to-checkpoint directory) in Structured Streaming, With the stoppage of the streaming job, all state data around the streaming job is lost and on the restart, the job must start from scratch.
Option B is incorrect. The given statement is not the potential result of not specifying the command option ("checkpointLocation", pointer-to-checkpoint directory) in Structured Streaming.
Option C is incorrect. The statement is not a potential outcome of the given scenario.
Option D is incorrect. The given statement is not the potential result of not specifying the command option ("checkpointLocation", pointer-to-checkpoint directory) in Structured Streaming.
Reference:
To know more about checkpoint storage in structured streaming, please visit the below-given link: 

https://www.waitingforcode.com/apache-spark-structured-streaming/checkpoint-storage-structured-streaming/read