Part 4 Full Quiz

B is correct. Without a coalesce field, ServiceNow has no way to match incoming rows against existing records. Every row is treated as a brand-new unique record and inserted, causing severe duplication. Coalesce designates one or more fields as unique keys (e.g., email address) so the transform can decide: update the existing record if the key matches, or insert a new record if no match exists. A is wrong because updating requires coalescing. C is wrong because the transform does not fail — it runs successfully but creates duplicates. D is wrong because ServiceNow never auto-merges on email unless you explicitly set that field as the coalesce key.

C is correct. A Data Source defines the origin of the data — including the protocol (SFTP, REST, JDBC, XML, Excel), the endpoint address, authentication credentials, and the file format. A Transform Map maps staging fields to target table fields after data has already been loaded into the Import Set Table. The Import Set Table (B) is the temporary staging table where raw rows land. A Business Rule (D) is server-side logic triggered on database events — it is not used to configure data origins.

B is correct. The Import Set Table is a temporary staging table that extends sys_import_set_row. It holds raw imported data before the Transform Map runs. After transformation, these rows remain until manually cleaned or auto-cleaned by a scheduled job. A is wrong because it is not permanent production data. C describes a Transform Map, not the Import Set Table. D is wrong because the Import Set Table is not an audit archive.

B is correct. Dependency Views in the CMDB provide a graphical diagram showing upstream and downstream CI relationships — exactly what a change manager needs to assess impact. The CI list view (A) shows flat records, not a relationship graph. Transform Map visualizer (C) does not exist as a standard CMDB tool. Service Portal widgets (D) are for end-user self-service, not CMDB impact analysis.

B is correct. The CMDB's power lies in its relationships — CIs are linked to Change requests, Incidents, Problems, and other CIs, enabling impact analysis, root cause analysis, and change governance workflows. Static asset tracking (cost, serial number) does not provide this relational context. A is wrong: both asset records and CIs can store financial data. C is wrong: the CMDB does not patch systems. D is wrong: asset and CMDB records coexist.

C is correct. The table cmdb_rel_ci stores CI relationship records, containing three key fields: Parent CI, Relationship Type (e.g. "Runs on", "Hosted on"), and Child CI. cmdb_ci (A) is the base CI table that stores individual configuration items, not their relationships. sys_relationship (B) does not exist as a standard ServiceNow table in this context. sys_cmdb_map (D) is not a standard ServiceNow table name.

B is correct. Field-level ACLs (table.field_name) and table-level ACLs (table.None) are separate and evaluated independently. A field ACL restricts access to that single field only — it does not control access to the record itself. The incident table likely has a permissive table-level ACL allowing all authenticated users to read records. A is wrong because field ACLs do not grant table access. C is wrong because field ACLs work without High Security. D is wrong because ACLs apply to all CRUD operations including read.

C is correct. ACL evaluation follows a fail-closed model evaluated in order: Role → Condition → Script. ALL three elements must pass for access to be granted. If any single element returns false, access is denied — regardless of whether the other elements passed. This is a critical CSA exam concept. A and B are wrong because the fail-closed model means any single failure denies access. D is wrong because the script failing alone is sufficient to deny access.

A is correct. The High Security plugin adds the requirement that security_admin role elevation is needed to modify ACL records. Critically, this elevation is session-only — the user must check "Elevate Privilege" in their user menu each time they log in, and the privilege does NOT persist across sessions. This is the trap: B is wrong because permanently assigning security_admin defeats the purpose of session-limited elevation. C is wrong because ACL records cannot be reliably self-protected this way. D is wrong because Business Rules can be bypassed by elevated admins.

B is correct. A wildcard ACL (table_name.*) applies to any field on that table that does NOT have its own explicit field-level ACL rule. It acts as a catch-all for fields, not for the record itself. A is wrong — the record-level ACL is table_name.None (with the literal word "None"), not the asterisk. C is wrong because the wildcard applies to fields of one table, not multiple tables. D is wrong because mandatory fields have no special ACL relationship.

C is correct. The sys_audit table records field-level changes including: which field changed, the previous value, the new value, the timestamp, and the user who made the change. Auditing must be enabled per table in the data dictionary. sys_log (A) stores system log messages, not field-change history. sys_history_set (B) is related to the History tab on forms (a visual journal), not the raw audit table. sys_archive (D) is the destination table for archived records moved by Data Archival Rules.

B is correct. This is a classic trap. sys_audit is one of the largest tables in any ServiceNow instance — it accumulates millions of rows over time. Querying it synchronously from a Client Script on every form load causes extreme latency because the browser must wait for the server round-trip on a massive table with no pre-filtered result. Best practice: never query sys_audit from client scripts. Use server-side scripts, GlideAjax, or the built-in Activity Stream instead. A is wrong — Client Scripts can use GlideRecord to query tables, though it is discouraged for large tables. C and D are distractors unrelated to this scenario.

B is correct. Data Archival Rules are specifically designed to move records that meet certain criteria (e.g., resolved more than 2 years ago) from the active production table to the sys_archive table. This dramatically reduces the size of the active table and improves query performance, while still retaining the records for compliance. ACL Archival Rules (A) do not exist as a ServiceNow feature. Transform Maps (C) are for importing data, not archiving. Activity Stream purge (D) clears journal entries, not full incident records.

C is correct. The Activity Stream is the real-time journal feed displayed on ServiceNow forms, showing comments, work notes, field changes, and system updates in chronological order. It is the user-facing presentation of record activity. The sys_audit viewer (A) is not a standard named UI element — sys_audit is a backend table. Dependency View (B) is the CMDB graphical impact diagram. Transform Log (D) is the log generated during an import transformation, not a form journal.

B is correct. The coalesce field is the unique key configuration on a Transform Map field mapping. When set, ServiceNow checks: "Does a record already exist in the target table where this field matches the incoming value?" If yes, it updates; if no, it inserts. Without coalesce, every row is blindly inserted. The "inserted: 200" result confirms no coalesce was set — otherwise 50 would show as "updated: 50." A scheduled cleanup job (A) deals with Import Set Table hygiene, not duplicates. The Data Source (C) was already working since data loaded successfully. An ACL (D) would block all writes, not selectively cause duplicates.