1. Behavior of cloudFiles.inferColumnTypes with and without cloudFiles.inferSchema:
   When cloudFiles.inferColumnTypes is enabled, Auto Loader attempts to identify the appropriate data types for columns instead of defaulting everything to strings, which is the default behavior for file formats like JSON, CSV, and XML.
   Without enabling cloudFiles.inferSchema, Auto Loader does not perform automatic schema inference. Instead, users must provide a schema explicitly or use schema hints. When both cloudFiles.inferColumnTypes and cloudFiles.inferSchema are enabled together, Auto Loader performs full schema inference on the incoming data, determining appropriate column data types based on the sampled data. This is especially useful for file formats lacking inherent type encoding (e.g., CSV, JSON).
   Why use both: The combination is beneficial when you want Auto Loader to infer both the schema structure (new columns, changes) and column data types dynamically, reducing manual intervention in managing schema during ingestion.
2.  
3. Using cloudFiles.inferColumnTypes without a schema checkpoint and its behavior:
   The cloudFiles.inferColumnTypes option can technically be enabled without specifying a schema checkpoint (cloudFiles.schemaLocation), but this setup is not recommended. Without a schema checkpoint, inferred schema changes cannot be tracked or persisted across runs, leading to potential issues when new data arrives with schema alterations.
   The schema checkpoint enables Auto Loader to persist schema evolution information and manage additions like new columns or changes in the data structure across micro-batches. Without a schema checkpoint, the behavior of cloudFiles.inferColumnTypes is limited to inferring column types for the current batch or sample scope, and schema consistency is the user’s responsibility.
   Using both cloudFiles.inferColumnTypes and a schema checkpoint allows seamless management of schema evolution while ensuring column types are accurately inferred and tracked. Missing checkpoint information may result in redundant inference and susceptibility to runtime errors if data evolves unexpectedly.

Hope this helps. BigRoux.