Why do we suggest dropping indexes before writing to databases?

• A. Writing with an existing index can lead to index-related errors.
• B. The database will reject features with existing index values.
• C. The index has to be provided to the database in a separate writing procedure.
• D. The database automatically updates the index with every feature that is written.

Answer: (D)

Dropping indexes before a bulk write is about avoiding the extra work the database does to keep those indexes up to date as data is inserted. Each inserted row can trigger updates to every relevant index, which adds I/O and processing time. By removing the indexes, you bypass that maintenance cost during the load, making the write faster. After the load finishes, you rebuild the indexes so queries benefit from them again. The chosen statement reflects this maintenance behavior: the database updates the index automatically with every feature written, which is exactly the overhead you’re trying to avoid during bulk loading. The other options don’t capture this dynamic of index maintenance during writes.