Features Per Transaction must always be equal to or a multiple of Features Per Bulk Write.

Features Per Transaction must always be equal to or a multiple of Features Per Bulk Write.

• A. TRUE
• B. FALSE
• C. Depends on data
• D. Not applicable.

Answer: (B)

Features Per Transaction and Features Per Bulk Write are independent controls that operate in different parts of the write process. Features Per Transaction sets how many features are processed before the writer starts a new transaction, while Features Per Bulk Write determines how many features are written in a single bulk operation to the destination. Because they are independent, there's no requirement that these numbers be equal or in a multiple relationship. For example, you could have a transaction boundary at 200 features but a bulk write size of 50, which would yield four bulk writes within that single transaction. Alternatively, you could have a large bulk write size but a small transaction boundary, causing multiple transactions to occur as features accumulate toward the bulk write size. Thus the statement is not universally true.

Features Per Transaction and Features Per Bulk Write are independent controls that operate in different parts of the write process. Features Per Transaction sets how many features are processed before the writer starts a new transaction, while Features Per Bulk Write determines how many features are written in a single bulk operation to the destination.

Because they are independent, there's no requirement that these numbers be equal or in a multiple relationship. For example, you could have a transaction boundary at 200 features but a bulk write size of 50, which would yield four bulk writes within that single transaction. Alternatively, you could have a large bulk write size but a small transaction boundary, causing multiple transactions to occur as features accumulate toward the bulk write size.

Thus the statement is not universally true.