In Field-Level Encryption Data Imports, which API calls are available?

In Field-Level Encryption Data Imports, which API calls are available?

• A. CreateRow; UpdateRow
• B. Lookup; InsertDE
• C. InsertDE; UpsertDE
• D. CreateRow; Lookup

Answer: (A)

Field-Level Encryption Data Imports are designed around modifying rows directly in a Data Extension. The only API calls that align with that row-level modification are creating a new row and updating an existing one. When data is encrypted at the field level, the import workflow relies on these two operations to ensure encrypted fields are handled consistently as part of the row-write process. Lookup is a read operation, so it doesn’t import or modify data. InsertDE and UpsertDE belong to other import interfaces and aren’t part of the Field-Level Encryption Data Imports surface, so they aren’t available in this context.

Field-Level Encryption Data Imports are designed around modifying rows directly in a Data Extension. The only API calls that align with that row-level modification are creating a new row and updating an existing one. When data is encrypted at the field level, the import workflow relies on these two operations to ensure encrypted fields are handled consistently as part of the row-write process.

Lookup is a read operation, so it doesn’t import or modify data. InsertDE and UpsertDE belong to other import interfaces and aren’t part of the Field-Level Encryption Data Imports surface, so they aren’t available in this context.