CCNA Account And Contact Management Questions

The Consumer Service Portal ships with a household data model that links consumers through defined member relationships, letting agents view and manage family or household groupings without custom development. This out-of-the-box capability satisfies the stem's requirement for features provided natively, rather than requiring configuration or plugins.

Matching multiple accounts leaves the case's customer field unpopulated, or flags it for manual agent review, because CSM cannot safely infer a single account from an ambiguous domain. This satisfies the stem's default behaviour constraint: resolution requires a unique match, so ambiguity defers to the agent rather than guessing.

The Account Contact relationship lets one contact link to multiple accounts, so the existing user contact can be associated with the new account without duplication. This satisfies the scenario while preserving the contact's existing account linkage.

Entitlements are fundamentally tied to customer accounts.

The consumer-based model treats individuals as consumers directly on the consumer table rather than grouping them under corporate accounts.

Cases raised for an individual buying for personal use use the Consumer record type, which stores personal contact details rather than a business Account. Selecting Consumer populates the Account/Consumer field correctly, satisfying the stem's personal-use constraint.

Account Hierarchy provides the parent–child account tree that customer service managers need to view and manage corporate relationships, satisfying the stem's requirement for hierarchical structure visibility. Unlike related modules such as Account Relationships, it specifically renders the multi-level account structure, enabling managers to navigate and administer linked parent and subsidiary accounts directly.

By adding a reference field to the case creation form that references the Account table and is filtered to show only accounts associated with the logged-in contact through the Customer Relationship table, the contact can select the appropriate account. This is a standard customization using form design and reference qualifiers.

The Company field on a contact record is a reference to the Account (customer_account) record and is the field that binds the contact to the business customer. When this reference is populated, the contact is treated as belonging to that account, so the contact can leverage the account's entitlements and raise cases against it from the Customer Service Portal.

When a consumer becomes affiliated with a business customer, the standard pattern is to create a contact record linked to that account and associate the person accordingly, so their prior cases remain accessible while new activity gains account context. This preserves history and avoids duplicate identities, and it is a routine consideration when planning portal experiences for mixed requester populations.

The Consumer record type represents individual customers who are not affiliated with a corporate account, enabling them to submit service requests directly. This satisfies the stem's requirement for individual consumers outside corporate accounts, unlike Business Account or Contact records.

The portal derives the case's Account from the submitting contact's parent account record, so the lookup populates automatically without manual entry. This satisfies the scenario's automatic population requirement by inheriting the contact-to-account relationship stored in the CRM data model.

Contacts link to a business account record, while consumers represent individual people. This satisfies the stem's distinction: contacts are account-scoped entities tied to a company, whereas consumers exist independently as person records, so the axis of difference is business-account association versus individual identity.

Active entitlements, their account linkage and expiration dates are stored as records in the Entitlement table, making it the authoritative source for this query. Reporting from it directly satisfies the requirement to list entitlements nearing expiry for a chosen account.

A Flow Designer flow triggered on the Account status field changing to 'Hold' can update related open cases and send notifications in one automated sequence. Workflow rules alone cannot reliably update child records and notify agents together.

Entitlements link to service contracts, letting you group them so coverage is inherited from the contract rather than defined per entitlement. This satisfies the stem's requirement for a genuine Entitlements feature, since contract-level grouping governs which customers or assets qualify for specific support terms.

Marking an account inactive blocks portal case submission because the Customer Service Management portal validates the account's active status before allowing a new case record to be created. This satisfies the stem's constraint that the account is inactive, preventing further inbound cases while preserving the existing case history for reference.

The Customer Relationship table models many-to-many links between accounts, so it suits peer or joint-venture arrangements where neither party is a subsidiary. The Account Parent field only expresses a strict hierarchical parent-child relationship, which cannot represent these reciprocal associations.

A consumer record is designed for individual requesters who are not associated with a business account, which matches this caller exactly. By creating a consumer, the agent captures the person's details, allows them to submit and track complaints through the Customer Service Portal, and keeps the account table reserved for genuine business customers with contracts and entitlements.

Last name is a mandatory field on the Customer Contact record, satisfying the stem's requirement for standard fields. ServiceNow enforces it at the schema level, so a contact cannot be saved without it, unlike optional fields such as mobile phone or job title. This makes it a core identifying attribute for contact records.

Setting the Parent field on Company B's account to Company A creates the corporate hierarchy while preserving Company B's existing records and case history. This satisfies the requirement to reflect subsidiary status without data loss, since the account itself remains intact and only its hierarchical relationship changes.

An internal service agent can populate the Account field manually while creating the case, selecting the relevant account from the record. This satisfies the stem as one valid population method, alongside automatic derivation from the caller or related records.

The Account field links the case to the business account record experiencing the issue, establishing which customer the support request concerns. This lets agents track all cases for that organisation and drives entitlements and service-level agreements tied to that account.

REST or SOAP Web Services APIs provide programmatic, bulk record creation into CSM tables, satisfying the legacy import requirement without manual entry. They support scheduled, repeatable loads and field mapping, making them a valid import method alongside import sets and templates.

The Account hierarchy related list stores the parent-child linkage between the global enterprise account and each subsidiary, so CSM can roll up cases, entitlements and contacts. It directly satisfies the stem's requirement for multiple subsidiaries reporting to one global account.

Customer relationships define connections between accounts, such as partner-to-customer links.

Accounts model organisations and therefore support multiple linked contacts, each with their own roles and relationships. Consumers are individual end users with a single record and no contact hierarchy, matching the stem's requirement to distinguish the two entity types in CSM data modelling.

The Account Tier field on the Account record stores the tier classification, letting portal routing rules identify tier-one accounts and prioritise their contacts on login. Recording tier elsewhere would not drive the required entitlement-based handling.

ServiceNow supports many-to-many contact-account associations through contact relationships and the contact-account mapping table, so one individual can serve several organisations. This satisfies the stem's requirement for a true statement about account-contact relationships, since the model is not restricted to a single account per contact.

Portal case submission requires the contact's user account to hold the appropriate portal roles, such as sn_customerservice.customer, which grant create access on the Case table. This satisfies the stem's condition that the contact possesses the necessary portal user roles.

Creating a distinct account for each division and assigning Contoso as the Parent builds a standard account hierarchy. Each division can then hold its own contacts, contracts, and entitlements for independent case tracking, while the Parent reference lets reporting and roll-up logic aggregate division activity up to Contoso without duplicating records or custom fields.

The Customer Relationship table is specifically designed to model many-to-many relationships between contacts and accounts. By creating a record in this table for each account the contact is associated with, the administrator enables the same contact to be linked to multiple companies without duplicating the contact record.

Installed Base items (assets) carry an Account reference, tying each customer's deployed products to their account record. This direct association supports entitlement checks and case resolution, satisfying the stem's requirement for record types linked to an Account.

A Service Contract groups entitlements and coverage terms for an account, defining what support a customer receives and when. It satisfies the stem's requirement by acting as the container that binds entitlements to an account, enabling CSM to validate coverage during case creation and enforce service-level commitments.

Deactivating the linked sys_user record sets Active to false, which invalidates the contact's portal authentication and terminates existing sessions, because portal login checks the underlying user account's active state rather than the contact record alone.

A Flow Designer flow triggered on the Contact table fires when a contact is created, and can conditionally generate an approval task for the account manager. This satisfies the requirement for automatic approval generation on strategic-account contacts.

Account hierarchy lets the case reference the subsidiary as the account while the entitlement resolves through the parent's contract. Setting Account to the subsidiary and choosing a parent-linked entitlement satisfies the requirement to bill the parent corporation.

The customer_account table underpins the account-based service model, acting as the primary container that groups business customers and their related contacts, cases and entitlements. Unlike consumer records, accounts represent organisations, so this table satisfies the stem's requirement for the organisational container in ServiceNow CSM.

The Account record includes a Contacts related list that shows all contacts associated with that account. This allows the agent to quickly view and access other contacts, such as subject matter experts, without leaving the account context. It is the standard and efficient way to see all contacts for an account.

When a case is created through the CSM portal, the system automatically populates the Contact field with the contact record linked to the authenticated user. This ensures the case is related to the correct contact without manual entry. The administrator should verify that the portal's case creation logic correctly maps the logged-in user to their contact record, which is the standard behavior in CSM.

The Domain Path [sys_domain] field on the Account record enforces isolation by assigning each account to a domain within the domain hierarchy. Regional service agents inherit visibility only from their own domain, so accounts outside their geographic branch remain hidden, satisfying the requirement that agents view solely their region's accounts.

Entitlements can be explicitly tied to an Account, defining what products or services that customer organisation is entitled to consume. This satisfies the stem's requirement, alongside Contact and Consumer as the other supported entity types.

Deduplication rules detect matching records by email and other fields, and merging consolidates the duplicates into one master contact, preserving related activities and history. This removes the ambiguity caused by slightly different email spellings without losing data.

Linking the Entitlement to Asset establishes the consumption relationship, so resolving a case against a covered asset decrements the account's remaining units. Without this field relationship, entitlement usage cannot be tracked against specific assets, and automatic decrementing on case resolution will not occur.

Account Tier records service level such as Tier 1 or Tier 2, driving entitlement, escalation and support priority. It satisfies the stem's categorisation requirement by ranking accounts on value or service commitment, a different axis from type or geography.

The Customer Relationship [customer_relationship] table stores peer and partner links between accounts, satisfying the requirement to establish non-hierarchical relationships. Unlike the account hierarchy, which handles parent-child structures, this table defines lateral connections such as partner or peer associations, directly meeting the stem's need for relationship methods between accounts.

Entitlement consumption can be metered by time or effort rather than per-incident, so elapsed hours or logged effort decrement the entitled units. This satisfies the stem's requirement for how units are consumed when cases are created, reflecting effort-based rather than flat-rate deduction.

Entitlement configuration defines which product models a contact may select. When an unsupported model is chosen, CSM either blocks submission outright or flags the case as out-of-entitlement, depending on the configured enforcement setting, satisfying the negotiated model-specific entitlement constraint.