Which import-set practice best aligns with official performance guidance for large loads

ACombine all source files into one massive import to reduce scheduling overhead

BBreak large imports into smaller sets and prefer coalesce over custom scripts when possible

CAdd GlideRecord lookups in every field map so each row can validate itself

DAlways run business rules on every imported row regardless of volume

Related Questions

To import external data into a production table through the standard ServiceNow import pattern, what...

easy

For inbound application data from another system, what does ServiceNow recommend instead of writing ...

medium

Which ServiceNow capability gives a guided interface to define data sources, map source data to targ...

medium

A single source feed must populate multiple target tables efficiently. Why is a robust import set tr...

hard

When external records arrive through import sets, where do they land before transformation to target...

easy

View all Data Strategies questions

Educational Content — CertQnA practice questions are written against official exam objectives, covering the same domains tested on the real exam. All content is original and independent — not actual exam questions, not affiliated with any certification vendor. Learn more about our content policy

Discussion

Be the first to share your understanding of this concept

⚠️ Discussion is for concept clarification only. Do not share or request actual exam questions or answers.