Service-Con-201 Integration And Data Management — Timed 15 Questions

Question 1

A support manager needs to ensure that Case records owned by Tier 1 support queues are only visible to members of that specific queue and the management hierarchy. Which sharing mechanism should the administrator configure?

15 minute time limit — choose an answer to begin.

Accepted Answer

Criteria-based sharing rules. Queues can be assigned as owners of Case records. Sharing rules or organization-wide defaults (OWD) combined with queue membership dictate visibility, and criteria-based sharing rules can target queues or roles.

Answer

Role hierarchy bypass rules

Answer

Public Group territory assignment

Answer

Manual sharing by agents

Question 2

A consultant is configuring account hierarchy data access for a global support team. Child accounts should automatically inherit sharing settings from their parent accounts. Where is this behavior enabled?

Accepted Answer

Sharing Settings -> Account Settings -> Use Hierarchies for Account Access. Enterprise Territory Management or Account Hierarchies rely on sharing settings. Specifically, 'Parent Account' grants access using 'Grant Access Using Hierarchies' or Account Sharing Rules.

Answer

Sharing Settings -> Account Sharing Rules -> Default Access

Answer

Organization-Wide Defaults -> Account Hierarchies settings

Answer

Enterprise Territory Management Setup

Question 3

A customer service center integrates with an external billing platform. When a Case status changes to 'Escalated', billing details must be fetched synchronously and displayed immediately on the Case layout. Which integration tool fits this pattern?

Accepted Answer

Apex Callout invoked via Record-Triggered Flow. A synchronous callout to an external system is needed to fetch billing details immediately when a Case is escalated. An Apex Callout invoked via Record-Triggered Flow allows for synchronous execution: the flow triggers on the Case status change and calls an Apex method that performs the HTTP callout, then returns data to be displayed on the Case layout. This pattern ensures the data is fetched in real-time.

Answer

Salesforce-to-Salesforce connection

Answer

Outbound Message with Workflow Rule

Answer

Bulk API 2.0 job export

Question 4

Universal Containers wants customer service agents to view related Contact details in a subtab without leaving the primary Case tab in the Service Console. Which data model relationship supports this parent-child navigation?

Accepted Answer

Lookup Relationship. A Lookup Relationship creates a parent-child link between two objects, allowing the child record (e.g., Contact) to be displayed as a related list or subtab on the parent record (e.g., Case) in the Service Console. This supports navigation to related Contact details without leaving the primary Case tab. The relationship is loose (no automatic deletion or roll-up), which is appropriate for viewing related details.

Answer

Roll-up Summary field

Answer

Cross-object formula field

Answer

External ID text mapping

Question 5

A Service Cloud consultant is designing a custom integration where external legacy ticket IDs must be matched to Salesforce Cases during high-volume nightly batch upserts. Which field attribute must be configured on the external ID field in Salesforce?

Accepted Answer

Text (External ID) and Unique. For high-volume nightly batch upserts matching external legacy ticket IDs to Salesforce Cases, the external ID field must be a Text field marked as External ID and Unique. The External ID attribute enables the field to be used in upsert operations via the API, while Unique ensures no two records share the same external identifier, preventing duplicate matches during batch processing.

Answer

Formula (Text) and Unique

Answer

Master-Detail relationship

Answer

Auto-Number and External ID

Question 6

An administrator needs to restrict access to sensitive customer service records so that only users assigned to the 'VIP Support' profile can view Cases marked with a 'High Priority' flag. Which feature should be used?

Accepted Answer

Criteria-based Sharing Rule. Criteria-based Sharing Rules grant record access to users based on field criteria (e.g., Priority = 'High') and can be targeted to a public group or role containing the VIP Support profile users. This is the declarative mechanism for conditionally sharing records with specific users without changing OWD.

Answer

Public Group membership rules

Answer

Organization-Wide Default modification to Public Read/Write

Answer

Manual sharing via user profile assignment

Question 7

An external ERP system needs to push shipment tracking updates into Salesforce and associate them with existing Cases. The external system does not know the Salesforce internal 18-character Case ID. What must the consultant configure on the Case object?

Accepted Answer

A custom field marked as External ID and Unique. To let an external system upsert records without knowing the Salesforce ID, you must define a custom field on the Case object marked as External ID and Unique. The external system can then use its own shipment tracking number as the external ID value in upsert operations, and Salesforce will match or create the Case accordingly.

Answer

A standard Auto-Number field

Answer

A cross-object formula field

Answer

A master-detail relationship field

Question 8

A Service Cloud consultant is integrating an external chat system with Salesforce Omni-Channel. Which architectural feature ensures chat transcripts map correctly to visitor records in Salesforce?

Accepted Answer

Omni-Channel Flow and Apex routing context. Omni-Channel Flow and Apex routing context provide the architectural mechanism to pass contextual data (such as visitor records or chat transcript identifiers) through the routing process. When integrating an external chat system, the routing context carries the visitor information so that the chat transcript can be correctly mapped to the visitor record in Salesforce.

Answer

Territory Management assignment rules

Answer

Standard Email-to-Case routing addresses

Answer

Bulk API data import wizard

Question 9

Universal Containers needs to configure complex sharing rules for Case records to ensure data privacy across regional divisions. Which THREE statements are true regarding Salesforce sharing rules? (Choose three.)

Accepted Answer

Sharing rules can never be used to restrict access more than the Organization-Wide Default.. Option C is correct because sharing rules are strictly an access-extending mechanism: they can only open up records beyond the Organization-Wide Default (OWD), never restrict access below it, so the most restrictive baseline is always the OWD. Option D is correct because criteria-based sharing rules evaluate field values on the record, and for Case records they can use standard fields (e.g., Status, Priority, Region__c-style custom fields) as filter criteria to share with users, roles, or public groups. Option E is correct because owner-based sharing rules share records owned by specified users or roles with other users, roles, or public groups, effectively granting access based on record ownership. Option A is wrong because sharing rules do not bypass Field-Level Security; FLS still hides fields even when a user has record access. Option B is wrong because sharing rules are evaluated asynchronously by the sharing recalculation process, not synchronously before record-creation triggers.

Answer

Sharing rules automatically bypass all profile-level Field-Level Security restrictions.

Answer

Sharing rules execute synchronously in real-time before record creation triggers.

Question 10

An enterprise support center is designing a data integration framework where external systems query Case data in real-time. Which THREE API options should the consultant consider? (Choose three.)

Accepted Answer

Bulk API 2.0 for asynchronous processing of millions of records.. The scenario requires real-time querying of Case data by external systems, so the consultant should consider APIs designed for programmatic data access. Option C (Bulk API 2.0) is correct because it is purpose-built for asynchronous processing of very large data volumes, such as millions of records, making it suitable when the integration framework must handle high-volume batch or bulk data operations alongside real-time queries. Option D (SOAP API) is correct because it supports enterprise XML-based integrations and exposes WSDL definitions, which is appropriate for external enterprise systems that require strongly typed, contract-based web service integration with Salesforce Case data. Option E (REST API) is correct because it provides lightweight, JSON-based synchronous resource queries, which directly matches the requirement for external systems to query Case data in real time. Option A is not correct because standard outbound email handlers are for sending email notifications, not for returning REST query responses. Option B is not correct because the Chatter REST API is used for Chatter feeds, users, groups, and social features, not for updating standard object page layouts, which are metadata configured through the Metadata API or Setup.

Answer

Standard outbound email handlers for REST query responses.

Answer

Chatter REST API for updating standard object page layouts.

Question 11

Universal Containers wants to display real-time customer satisfaction scores from an external system on the Case detail page. The external system exposes a REST API that returns JSON. The scores change frequently and should not be stored in Salesforce. Which feature should the consultant use?

Accepted Answer

Use an Apex controller with a @AuraEnabled method that performs a callout and displays the score in a Lightning component on the Case page.. To display real-time external data without storing it, a Lightning component with an Apex controller is appropriate. The Apex controller makes a server-side callout, securely handles authentication, and returns the data to the component for display on the Case page. This meets the real-time and no-storage requirements.

Answer

Schedule a nightly batch job to fetch scores and update a custom field on the Case.

Answer

Salesforce Connect with an OData adapter to create an external object for the scores.

Answer

Create a custom Lightning component that makes a client-side callout to the REST API and displays the score on the Case page.

Question 12

A consultant is designing a nightly integration that loads 250,000 closed Case records from an on-premises data warehouse into Service Cloud for reporting. The load must complete within a maintenance window and must not trigger Case assignment rules, auto-response rules, or workflow email alerts. Which API and configuration should the consultant choose?

Accepted Answer

Bulk API 2.0 ingest job with the assignment rule, auto-response rule, and workflow rule options disabled. Bulk API 2.0 ingest jobs are built for high-volume asynchronous loading and expose job-level settings that disable assignment rules, auto-response rules, and workflow rules. That combination satisfies both the 250,000-record volume within a maintenance window and the requirement to avoid rule-driven side effects. REST composite, SOAP, and non-Bulk Data Loader approaches lack the scalability or the specific rule-suppression controls needed here.

Answer

A Data Loader command-line process using the insert operation with the 'Use Bulk API' option unchecked

Answer

REST API composite requests sent in parallel from the middleware with all rules left active

Answer

SOAP API with the AllOrNone header set to true and rules suppressed through a custom setting

Question 13

A consultant is planning a nightly bulk load of 500,000 closed Case records from an on-premises data warehouse into Service Cloud using the Bulk API 2.0. The source extract contains duplicate Case Numbers and a few records with malformed ClosedDate values. Which TWO practices should the consultant apply to make the load reliable? (Choose two.)

Accepted Answer

Use the Bulk API 2.0 ingest job with 'External ID' configured on Case Number so upserts match existing records instead of creating duplicates.. Reliable high-volume loading depends on idempotent matching and clean input. Configuring Case Number as an External ID and using Bulk API 2.0 upsert lets repeated identifiers update existing Cases rather than create duplicates, while pre-validating malformed ClosedDate values and reviewing the job's failed-records file keeps the load repeatable and correctable.

Answer

Raise the API request limit for the integration user's profile so all 500,000 records submit in a single request.

Answer

Enable the 'Assignment Rule' on the job so records are routed to the correct queue during ingestion.

Answer

Split the file into batches under 10,000 records and submit each as a separate Bulk API 2.0 job to avoid governor limits.

Question 14

A service team needs agents to see a customer's current subscription tier, which is maintained in an external subscription platform, on the Case record page. The external system exposes a REST endpoint, and the data must never be stored in Salesforce. The consultant must choose the lowest-maintenance declarative option that renders the value inside the Lightning record page. Which solution should the consultant recommend?

Accepted Answer

Build a Lightning web component that calls the REST endpoint and place it on the Case record page via Lightning App Builder.. Rendering a live external value without storing it is best achieved with a Lightning web component that calls the REST endpoint and is placed on the Case record page through Lightning App Builder. This keeps the data external, avoids batch synchronization and staleness, and requires only one deployable component rather than a full external data source configuration.

Answer

Schedule a nightly Data Loader export of subscription tiers into a custom field on the Account.

Answer

Create an External Object and relate it to Case, then add a related list to the Case Lightning page.

Answer

Configure a Salesforce-to-Salesforce connection and subscribe to the subscription platform's published tier field.

Question 15

An integration publishes Case updates to an external analytics platform every time a Case is modified. During peak hours the external platform throttles requests and returns HTTP 429 responses, causing lost updates. The consultant needs a retry mechanism that does not block the agent's save and preserves ordering for the same Case. Which approach should the consultant recommend?

Accepted Answer

Use Platform Events published from a record-triggered flow, with an Apex subscriber that retries failed deliveries and tracks them in a custom object.. Publishing Platform Events from a record-triggered flow keeps the agent's save fast, and an Apex subscriber can retry throttled deliveries with backoff while logging attempts in a custom object for observability. Platform Events preserve publish order for a given record, so successive updates to the same Case are not reordered, satisfying the ordering requirement without blocking the UI.

Answer

Configure an Outbound Message on Case update and point it at the analytics platform's REST endpoint.

Answer

Invoke the callout synchronously in an after-update Apex trigger and retry in a loop until a 200 response is received.

Answer

Enable Change Data Capture on Case and let the analytics platform subscribe to the event stream directly.