Service-Con-201 Integration And Data Management Practice Test 3 — 15 Questions

Question 1

A service center is migrating 50 million legacy customer interactions into Salesforce Service Cloud. To optimize SOQL query performance and data storage indexing for custom reporting, what should the administrator configure?

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

Custom indexes requested via Salesforce Support. For large data volumes like 50 million records, Salesforce recommends requesting custom indexes via Salesforce Support to improve SOQL query performance on fields frequently used in WHERE clauses, ORDER BY, or joins. Custom indexes are created by Salesforce (not the admin) and are essential when standard indexes are insufficient for selective queries on large objects.

Answer

External object mappings via OData

Answer

Standard auto-number primary keys

Answer

Classic encrypted custom text fields

Question 2

Universal Containers requires that whenever a critical Case is created, an event message is published to an external enterprise bus in real-time. Which feature should the consultant implement?

Accepted Answer

Platform Events published via Flow or Apex. Platform Events support publishing custom event messages in real-time to integrate Salesforce with external bus architectures.

Answer

Nightly batch export using Bulk API

Answer

Chatter feed item webhook notifications

Answer

Standard outbound messaging via workflow

Question 3

A support manager wants to ensure that agents can view Account details on a Case without having direct edit access to the underlying Account record. Which organization-wide default setting supports this?

Accepted Answer

Account OWD set to Public Read Only. Setting Account OWD to Public Read Only allows all users to view Account records while preventing them from editing unless they have edit access via role hierarchy, sharing rules, or profile/permission set. This satisfies the requirement of viewing Account details on a Case without edit access.

Answer

Account OWD set to Private with full hierarchy access

Answer

Account OWD set to Controlled by Parent

Answer

Account OWD set to Public Read/Write

Question 4

A consultant is designing a data model for a multi-channel customer service center. Which TWO design considerations are critical when relating Cases to Assets and Work Orders? (Choose two.)

Accepted Answer

Ensure Work Orders are linked to Cases to manage field service tasks and maintenance history.. Option A is correct because linking Work Orders to Cases lets the service center track field service tasks and the maintenance history associated with a customer issue, which is essential in a multi-channel service model where cases often spawn on-site work. Option C is correct because a Lookup relationship from Case to Asset identifies the specific product or equipment the case concerns, enabling asset-based tracking and reporting without imposing the restrictive ownership semantics of master-detail. Option B is not appropriate here because the question asks about relating Cases to Assets and Work Orders, not configuring Accounts as a master in a master-detail with Cases, and such a relationship would not address the asset/work-order linkage. Option D is wrong because deliberately avoiding relationships would prevent the cross-object visibility and history the scenario requires. Option E is wrong because automatically deleting historical Assets when an Account changes would destroy service and maintenance records, violating data retention and audit needs.

Answer

Configure Cases as master objects in a master-detail relationship with Accounts.

Answer

Avoid establishing any relationships between Cases and other objects to maximize storage limits.

Answer

Delete all historical Assets automatically whenever a parent Account is modified.

Question 5

Universal Containers integrates its telephony system with Service Cloud and needs to ensure secure, reliable data exchange and proper record linkage. Which TWO integration best practices should the consultant recommend? (Choose two.)

Accepted Answer

Store endpoint URLs and authentication tokens securely using Named Credentials.. Option A is correct because Named Credentials store endpoint URLs and authentication tokens securely, keeping credentials out of Apex code and enabling Salesforce to handle authentication for callouts to the telephony system. Option E is correct because External ID fields let upsert operations match incoming telephony records to existing Salesforce records, preventing duplicate creation and ensuring proper record linkage. Option B is incorrect because synchronous REST callouts are not suited to high-volume batch loads and can hit governor limits, so asynchronous or Bulk API approaches are preferred. Option C is incorrect because hardcoding tokens in Apex triggers is insecure and exposes credentials in source code. Option D is incorrect because disabling organization-wide sharing defaults during API loads is not a security best practice and does not improve integration reliability.

Answer

Rely exclusively on synchronous REST callouts for all high-volume batch data loads.

Answer

Hardcode authentication tokens directly in Apex trigger classes for speed.

Answer

Disable all organization-wide sharing defaults during API data loads.

Question 6

A service organization is evaluating data archiving strategies for millions of closed Cases. Which TWO features should the consultant evaluate for long-term data retention and access? (Choose two.)

Accepted Answer

Big Objects for native, scalable storage and custom SOQL querying of historical cases.. Option A is correct because Big Objects provide native, scalable storage on the Salesforce platform designed for very large data volumes (billions of records) and support asynchronous SOQL queries against that historical data, making them suitable for retaining millions of closed Cases long-term. Option B is correct because Salesforce Connect uses external objects and OData/REST adapters to surface data stored outside Salesforce (for example, in an external database or data lake), letting the organization archive records beyond standard storage limits while still accessing them through the Salesforce UI and relationships. Option C is not appropriate because a workflow rule that overwrites the Case Description with the word 'Archived' destroys the original data rather than retaining it, which defeats long-term retention. Option D is not appropriate because page layout rules only control how fields are displayed to users and have no bearing on data storage, retention, or archival. Option E is not appropriate because manually deleting historical records with Data Loader permanently removes the data and is neither a retention nor an access strategy.

Answer

Workflow rule field updates to overwrite case descriptions with the word 'Archived'.

Answer

Standard Case object page layout rule overrides for archiving.

Answer

Daily manual deletion of all historical records using Data Loader.

Question 7

An enterprise Service Cloud implementation requires integrating an external billing system using REST APIs. Security and performance are top priorities. Which THREE practices should the consultant incorporate into the design? (Choose three.)

Accepted Answer

Implement robust error handling and logging mechanisms in Apex for failed callouts.. Option A is correct because robust error handling and logging in Apex (e.g., try/catch around HttpRequest/Http.send, custom logging objects, and Platform Events) are essential for diagnosing failed REST callouts and maintaining integration reliability in a security-sensitive billing integration. Option D is correct because asynchronous callouts (e.g., @future(callout=true), Queueable with HttpCallout, or Batch Apex) prevent blocking of synchronous transactions and governor-limit exhaustion, which is critical for high-volume, performance-focused integrations. Option E is correct because Named Credentials and External Credentials store endpoint URLs and authentication securely, support OAuth/JWT and other protocols, and remove secrets from code, directly satisfying the security priority. Option B is incorrect because hardcoding session tokens in Custom Metadata Types exposes credentials in source control and metadata deployments, violating security best practices. Option C is incorrect because synchronous callouts are not allowed in before-insert triggers and would block the transaction, harm performance, and risk governor-limit failures.

Answer

Hardcode session tokens in custom metadata types for quick retrieval.

Answer

Execute all external integrations synchronously inside standard before-insert triggers.

Question 8

A consultant is configuring data access for a customer service team where agents belong to various public groups and territories. Which TWO mechanisms determine a user's ultimate record access in Salesforce? (Choose two.)

Accepted Answer

Role Hierarchies granting access to records owned by subordinates.. Option B is correct because the role hierarchy in Salesforce grants users access to records owned by users below them in the hierarchy, which is a core mechanism for determining record-level access, especially for managers and subordinates. Option D is correct because Organization-Wide Defaults (OWD) set the baseline (most restrictive) level of record access for all users, which is then extended by other sharing mechanisms. Option A is incorrect because profile layout assignments and tab visibility control the user interface and object-level permissions, not record-level access. Option C is incorrect because Chatter group membership affects collaboration and feed visibility, not record access to standard or custom objects. Option E is incorrect because Omni-Channel routing configurations determine how work items are routed to agents, not the underlying record access permissions.

Answer

Profile layout assignments controlling tab visibility.

Answer

Chatter group membership settings.

Answer

Omni-Channel routing configurations.

Question 9

An enterprise customer service desk requires high-volume data integration from an external legacy ticket system. Which THREE considerations are vital when using the Salesforce Bulk API? (Choose three.)

Accepted Answer

External ID fields must be specified when performing upsert operations.. Option C is correct because Bulk API upsert operations require an External ID field to match incoming records against existing Salesforce records, since the legacy ticket system's identifiers are not Salesforce record IDs. Option D is correct because Bulk API is designed for asynchronous, batch-based processing, splitting jobs into batches that are queued and processed in the background, which is what enables handling of millions of records without hitting synchronous API limits. Option E is correct because Bulk API supports both CSV and JSON payload formats for job data, with CSV being the traditional format and JSON supported in Bulk API 2.0. Option A is not correct because Bulk API is asynchronous and not intended for real-time synchronous UI updates such as agent screen pops; those would use Streaming API, Platform Events, or a synchronous API. Option B is not correct because Bulk API does not automatically bypass Apex triggers or validation rules; those still execute unless explicitly disabled or unless the operation uses a mechanism that skips them, so this blanket statement is false.

Answer

Bulk API supports real-time synchronous UI updates for agent screen pops.

Answer

Bulk API jobs bypass all Apex triggers and validation rules automatically.

Question 10

A service administrator wants to ensure data integrity when agents create Cases associated with Accounts and Contacts. Which TWO data model validation practices should be implemented? (Choose two.)

Accepted Answer

Write Validation Rules to enforce required field completion based on Case Status.. Option A is correct because Validation Rules provide server-side, declarative enforcement that required fields are populated based on Case Status, ensuring agents cannot save incomplete or inconsistent Cases regardless of entry point (UI, API, or agent console). Option E is correct because Lookup Filters on the Case Contact field constrain the available Contact records to those related to the selected Account, preserving referential integrity in the Account-Contact-Case relationship and preventing mismatched associations. Together these practices enforce data integrity at the data model level rather than relying on human behavior. Option B is incorrect because disabling standard validation rules removes integrity safeguards and risks corrupting data, and validation rules have negligible impact on API integration speed. Option C is incorrect because user training alone provides no technical enforcement and is error-prone. Option D is incorrect because converting lookups to text fields destroys relational integrity and eliminates the ability to enforce relationships or filters.

Answer

Disable all standard validation rules to speed up API data integration speeds.

Answer

Rely solely on user training without technical enforcement mechanisms.

Answer

Convert all lookup relationships to text fields to bypass data model constraints.

Question 11

Universal Containers needs to synchronize Case attachments with an external document management repository. Which THREE architectural components are necessary to build this integration? (Choose three.)

Accepted Answer

Asynchronous Apex (Queueable or Batch) to prevent callout blocking and governor limit exhaustion.. Option A is correct because file synchronization with an external repository involves HTTP callouts that cannot be performed in synchronous triggers, so Asynchronous Apex (Queueable or Batch) is needed to avoid blocking the transaction and to stay within governor limits such as the 100-callout limit and heap size. Option B is correct because Salesforce Files are stored as ContentDocument records with their binary data in ContentVersion, so querying ContentVersion and ContentDocument (including fields like VersionData, Title, and FileExtension) is the required way to retrieve the file metadata and binaries for synchronization. Option C is correct because transmitting file binaries to an external document management repository requires Apex REST callouts or HTTP integration services (e.g., HttpRequest/HttpResponse with multipart or base64 payloads) to move the data out of Salesforce. Option D is not correct because Workflow Rule outbound messaging sends SOAP messages with record field data and cannot stream binary file content, so it cannot synchronize attachments. Option E is not correct because Omni-Channel work item routing is a case/agent routing feature unrelated to document synchronization architecture.

Answer

Standard Workflow Rule outbound messaging for binary file streaming.

Answer

Real-time Omni-Channel work item routing rules.

Question 12

A consultant is troubleshooting data synchronization failures between an external ERP and Service Cloud. Which TWO diagnostic tools should the consultant use to investigate API errors? (Choose two.)

Accepted Answer

Event Monitoring REST API and log files to analyze API usage and failures.. Option A is correct because the Event Monitoring REST API exposes EventLogFile records (e.g., API, API Total Usage, and Login event types) that let the consultant quantify API call volumes, identify failed requests, and correlate them with log files to pinpoint the source of ERP synchronization errors. Option D is correct because Salesforce Debug Logs with the DB and CALLOUT trace flags capture the actual Apex execution, SOQL/DML statements, and outbound HTTP callout request/response details, which is essential for diagnosing why an integration callout to the external ERP is failing. Option B is not appropriate because Omni-Channel Supervisor metrics track agent presence, capacity, and work routing in real time, not API or integration errors. Option C is irrelevant since Knowledge article version history only tracks changes to article content and has no bearing on API troubleshooting. Option E is also irrelevant because Case History related lists show field-change tracking on a case record, not integration or API failure diagnostics.

Answer

Omni-Channel Supervisor real-time metrics dashboard.

Answer

Knowledge article version history.

Answer

Standard Case History related lists on individual records.

Question 13

A service manager needs to ensure that when a Case is closed, a summary record is sent to an external data warehouse. The warehouse exposes a REST API that accepts JSON payloads. The integration must be reliable and must not block the user from closing the Case. Which approach should the consultant use?

Accepted Answer

Publish a Platform Event when the Case is closed and have an Apex subscriber make an asynchronous callout to the warehouse API.. The requirement for non-blocking, reliable integration with a REST API is best met by using Platform Events. Publishing an event on Case closure triggers an asynchronous subscriber that performs the callout. This avoids blocking the user and allows for robust error handling. Synchronous callouts and Outbound Messages do not fit due to blocking or protocol mismatch.

Answer

Write an Apex trigger on Case that performs a synchronous callout to the warehouse API in an after update context.

Answer

Create a Process Builder that makes an HTTP callout to the warehouse API when the Case status changes to Closed.

Answer

Use an Outbound Message on the Case object to send the summary to the warehouse API.

Question 14

A consultant is configuring a real-time integration where Service Cloud must call an external REST API to validate a customer's subscription tier whenever an agent opens a Case record page. The external system authenticates callers using OAuth 2.0 and requires the Salesforce org to obtain an access token before each callout session. Which Salesforce feature should the consultant use to configure the outbound authentication and HTTP callout without writing Apex?

Accepted Answer

Named Credential with an External Credential and a permission set granting access to the principal. Outbound callouts that require OAuth 2.0 token acquisition are handled declaratively with Named Credentials paired with External Credentials, and access is controlled by assigning the External Credential principal via permission set. This keeps secrets out of code, supports token refresh, and can be invoked from Apex, Flow, or Lightning components on the Case page. Remote Site Settings, Auth. Providers, and Connected Apps serve different trust directions and do not provide outbound token management.

Answer

A Remote Site Setting pointing to the external API domain plus a hard-coded bearer token in the Apex controller

Answer

An Auth. Provider configured as an OpenID Connect provider referenced directly by the Case Lightning record page component

Answer

A Connected App in the external system with the Salesforce org added as a trusted IP range

Question 15

A service organization ingests Cases from an external partner portal through the REST API. The partner sometimes sends duplicate external IDs within a short window, creating duplicate Case records. The consultant must configure Salesforce to reject or update records based on a unique external identifier during the API upsert. Which capability should be configured to enforce this behavior?

Accepted Answer

An external ID field marked as unique on the Case object, used with the sObject upsert operation. Marking an external ID field as unique lets the REST upsert operation use that field as the match key, so repeated payloads update the existing Case instead of inserting duplicates. Uniqueness is enforced at the database level, making the integration idempotent without custom code. Duplicate rules, validation rules, and hard-error triggers do not integrate with upsert matching semantics and therefore do not deliver the required behavior.

Answer

A validation rule on the Case object that compares the external ID to existing records using a VLOOKUP formula

Answer

A duplicate rule with a matching rule on the Case external ID field set to block on create

Answer

A before-insert Apex trigger that queries for an existing Case with the same external ID and throws an error