When building advanced CMDB queries usingCMDB Query BuilderinServiceNow, the correct approach is to modelCI scope,relationships, andtask contextexplicitly on the canvas.
To limit results to databases in a specific location, the administrator mustfilter the Database CI nodeby the Location attribute. Therefore,Option Cis required to scope the query toDatabase CIs where Location = Seattle.
To includeIncidents related to those databases, the Incident table must be added from theNon-CMDB Tableslist and linked through thetask_cirelationship. This is exactly whatOption Aprovides. CMDB Query Builder separates CMDB tables (CIs) from task and transactional tables, so incidents must be explicitly added from the Non-CMDB section.
Option B is incorrect because property columns on Application Services do not scope databases or incidents.
Option D is unnecessary because relationship depth alone does not include non-CMDB task data and does not filter by location.
Thus, the correct actions areA (add Incident table)andC (filter Database by location).