CCNA Integration And Data Management Questions

Setting Account organisation-wide defaults to Public Read Only grants all users read access to every Account while restricting edit to owners and above. Agents can therefore view Account details from the Case without gaining edit rights, satisfying the manager's least-privilege requirement.

Salesforce Connect maps external objects to data held in an external system via an adapter, exposing it in the Console in real time without replicating records into Salesforce storage. This satisfies the no-storage constraint for external order history.

Criteria-based sharing rules grant access based on field values rather than ownership, so a rule matching Category equals 'Hardware' shares those private Cases with Tier 2 agents. This satisfies the requirement to automate read/write access by Category.

Queueable or Batch Apex runs the synchronisation outside the transaction, so HTTP callouts to the external repository never block the user request or breach synchronous callout and governor limits. This satisfies the bulk, non-blocking requirement.

Salesforce Connect with External Objects maps the external loyalty database via OData or cross-org adapters, surfacing records on the Account page in real time without copying data into Salesforce. This satisfies the no-replication constraint, since queries execute against the external source on demand rather than through scheduled sync or ETL.

Case Record Types let each regional department see only its own picklist values, while dependent picklists filter the child list based on the parent selection. Together they satisfy the requirement for unique categorisation values per region without exposing irrelevant options, and they enforce that filtering at the form level.

Selecting the lookup's delete behaviour to clear the field value removes the Contact reference on related Cases while preserving the Case records themselves. This satisfies the requirement that open Cases survive Contact deletion without their Contact link.

Case History tracking stores field-level change records, including OwnerId transitions between queues and agents, with timestamps and the user who made each change. This provides the historical ownership audit trail the compliance reporting scenario demands.

The role hierarchy grants users access to records owned by users beneath them in the role tree, regardless of organisation-wide default settings. It is one of the mechanisms that cumulatively determines a user's ultimate record access alongside sharing rules and manual sharing.

Bulk API upsert matches incoming records against an external ID field rather than the Salesforce record ID, so the legacy system's own identifier must be declared in the job. Without it, upsert cannot determine which existing records to update.

Big Objects store billions of records on the Salesforce platform, bypassing standard storage limits, and are queried with custom SOQL via Async SOQL. This satisfies the millions-of-closed-Cases retention requirement while keeping historical data accessible inside Salesforce.

Upsert matches incoming records against an external ID field; when that field is marked unique, Salesforce enforces uniqueness at the database level and prevents duplicate external identifiers. The API call then updates the existing Case or inserts a new one instead of creating a duplicate. This is the standard declarative way to make integration upserts idempotent, and it works regardless of which integration user performs the call.

Enabling Grant Access Using Hierarchies lets managers inherit access to records owned by users beneath them in the role hierarchy, regardless of organisation-wide defaults. This satisfies reassigning ownership across subordinate service teams without manual sharing rules.

A Lightning web component hosted on the Account record page can render both Salesforce data and external data side by side. The Apex controller uses a Named Credential to call the external system securely, and the external response is displayed without persisting records in Salesforce. This satisfies the real-time, no-storage requirement while keeping authentication declarative.

HTTP 401 indicates an authentication failure, which commonly stems from an expired or misconfigured OAuth token, disabled integration user, or incorrect credentials. Checking the integration user's login status and the token refresh logic in the middleware directly addresses this class of error. Because the failures are intermittent, token expiry at a specific interval is a likely cause, making this a targeted and appropriate diagnostic step.

An Apex Action invoked from a Screen Flow lets the button call the external REST API synchronously via callouts, then return the synced notes to the agent instantly. Screen Flows provide the clickable UI, while Apex handles the HTTP callout that Flow alone cannot perform.

Validation rules enforce field completion and data integrity at save time, blocking records that violate defined criteria. Writing rules tied to Case Status satisfies the requirement that Cases associated with Accounts and Contacts contain complete, valid data before agents commit them.

Custom indexes are created only by Salesforce Support, and they accelerate filtering and sorting on large custom fields. Requesting them satisfies the requirement to optimise SOQL performance and indexing across 50 million migrated interaction records.

Configuring Federated Search via an OpenSearch provider lets Salesforce query the external CMS at search time and surface those articles alongside native Knowledge results in the global search bar. This directly satisfies the requirement for external articles to appear in agent search without replicating content into Salesforce.

Event Monitoring's REST API exposes API usage and failure events, while log files capture request details, letting the consultant trace synchronisation errors between the ERP and Service Cloud. This satisfies the need to investigate API failures diagnostically.

A Permission Set layered onto a minimally provisioned profile is the standard way to grant exactly the object and field access an integration user needs, such as Create on Case, while denying everything else. Because profiles are additive with permission sets, removing all other object permissions from the profile ensures the integration user cannot read, edit, or delete unrelated records.

Apex Continuations keep the agent console responsive by suspending the callout and releasing the thread, resuming via callback once the external warranty service responds. This directly satisfies the stem's constraint of preventing console lockups during latency spikes, unlike synchronous callouts that block the transaction and freeze the agent interface.

Named Credentials combined with External Credentials define the endpoint URL and the authentication protocol, while the External Credential's principal handles the OAuth 2.0 token exchange. Assigning the External Credential principal through a permission set lets the integration run without exposing secrets in code. This is the declarative standard mechanism for outbound callout authentication in modern Salesforce releases, and it works for Apex, Flow, and other callout consumers on the Case record page.

Platform Events deliver the scalable publish-subscribe ingestion the stem demands: IoT devices publish high-frequency telemetry via the CometD or Pub/Sub API, and a subscribed Flow or Apex trigger evaluates thresholds and creates Case records automatically, decoupling producers from Salesforce processing limits.

Big Objects store massive datasets on the Salesforce platform with an index-based, NoSQL-style architecture, bypassing standard object storage limits. This satisfies the requirement to archive millions of closed Case records while retaining read-only access for auditing, since Big Objects support asynchronous SOQL queries against indexed fields without impacting report performance.

Linking Work Orders to Cases ties field service tasks and maintenance history to the customer's support record, giving agents visibility of asset servicing. This relationship is critical when modelling Cases alongside Assets and Work Orders across channels.

Robust Apex error handling and logging capture callout failures, timeouts and HTTP error responses, enabling retries and diagnosis. This satisfies the security and performance priorities by preventing silent data loss and exposing integration faults during external billing system REST calls.

Named Credentials store endpoint URLs and authentication tokens in a protected store, so callouts reference a named endpoint instead of hard-coded secrets in Apex or configuration. This satisfies the stem's requirement for secure, reliable data exchange with the telephony system.

Platform Events publish messages onto Salesforce's event bus, which external subscribers receive through CometD or Pub/Sub API in near real-time. This satisfies the requirement to notify an external enterprise bus immediately when a critical Case is created.

A dedicated External ID field populated with the legacy system's stable Contact identifier gives upsert a reliable, unique matching key that is unaffected by shared email addresses. Marking it Unique enforces integrity, and subsequent loads update the correct Contact instead of inserting duplicates. This is the standard pattern for repeatable migrations between systems.

An open CTI API lets the telephony platform push call events directly into the service desk in real time, triggering the screen pop on call arrival. Batch or replication-based patterns introduce latency that breaks the real-time requirement specified in the stem.

Upserting with an external ID field allows the external system to match records based on the order number and update the existing Case without needing the Salesforce ID. This prevents duplicate Case creation and ensures the status update is applied to the correct record, which is exactly the requirement in this scenario.

Platform Encryption with BYOK (Bring Your Own Key) lets the customer supply and control the tenant secret via a Hardware Security Module, so Salesforce cannot decrypt PII at rest. This directly satisfies the stem's requirement that encryption keys be managed exclusively by the customer.

Platform Events enable asynchronous, reliable communication. Publishing an event when a Case is closed decouples the user transaction from the callout. An Apex subscriber processes the event and makes the REST callout asynchronously, so the user is not blocked. This pattern also supports retries and error handling, meeting the reliability requirement.

Salesforce Connect allows real-time access to external data via external objects. A custom adapter can connect to the external knowledge base's API. The external articles can then be displayed in a related list or custom Lightning component on the Case page without being stored in Salesforce. This meets the requirement.