SNOW-CAD Creating and customizing tables and data Practice Question
When creating a custom table to extend an existing table, which TWO considerations should be evaluated to ensure optimal performance and maintainability? (Choose two.)
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The number of records in the parent table may impact query performance when retrieving child records
Options D and E are correct. When extending a table, the number of records in the parent table can impact query performance when retrieving child records because child tables inherit the parent table's data, and queries may need to scan the parent table as well. Adding too many fields to an extended table can degrade performance (more data to store and process) and increase complexity (harder to maintain relationships and ACLs). Option A is incorrect because while ServiceNow suggests a naming convention with 'u_' for custom tables, it is not a strict requirement for performance or maintainability. Option B is incorrect because the table should be created in the same scope as the application it belongs to, not necessarily global scope. Option C is incorrect because a reference field back to the parent table is not required; the table extension itself establishes the relationship via inheritance.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The table must have a unique name starting with 'u_'
Why it's wrong here
While naming convention is important, it is not a performance or maintainability consideration.
- ✗
The table should be created in the global scope to ensure universal access
Why it's wrong here
Scope is about application isolation, not performance or maintainability of table extension.
- ✗
The table must have a reference field back to the parent table
Why it's wrong here
Extended tables automatically inherit the parent's fields; a reference field is unnecessary and would create redundancy.
- ✓
The number of records in the parent table may impact query performance when retrieving child records
Why this is correct
When extending, queries often include parent table records, which can slow down if the parent table is large.
- ✓
Adding too many fields to the extended table can degrade performance and increase complexity
Why this is correct
Excessive fields, especially on a heavily used table, can slow down form loads and database operations.
Visual reference
Go deeper
Related to this question
About these practice questions
This SNOW-CAD question is part of Courseiva's 481-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SNOW-CAD practice question is part of Courseiva's free ServiceNow certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SNOW-CAD exam.