Important Salesforce Plat-Arch-204 Exam Questions

Answer: A

Explanation:

The scenario highlights vulnerabilities in unmanaged packages where secrets (usernames, passwords, OAuth tokens) are stored in plain text and easily accessible. The goal is to protect these secrets from exposure in callouts, especially in unpackaged or unmanaged code contexts.

Why A (Protected Custom Metadata Types and Named Credentials)?

Named Credentials is the primary Salesforce-recommended mechanism for securely storing authentication details (including passwords, tokens, and secrets) for HTTP callouts. Secrets are encrypted, not visible in debug logs, and Salesforce handles authentication without exposing them in Apex code.

However, in Named Credentials, admins with 'Customize Application' permission can view/edit the secrets.

To further protect secrets (e.g., hide them completely from admins or in packaged scenarios), use Protected Custom Metadata Types (preferably in a managed package). These allow Apex code in the same namespace/package to access the secrets while hiding them from users, API queries, or subscriber orgs.

This combination addresses both standard callouts (via Named Credentials) and cases needing maximum obfuscation (via Protected Custom Metadata), directly mitigating plain-text exposure in unmanaged packages.

Why not B (Encrypted Custom Fields and Protected Custom Settings)?

Encrypted Custom Fields are suitable for sensitive data like PII (e.g., credit cards, SSNs) but explicitly not recommended for storing authentication secrets or credentials used in callouts (per Salesforce Secure Coding guidelines).

Protected Custom Settings offer similar protection to Protected Custom Metadata but are less preferred for configuration-like data (secrets are configuration). Custom Metadata is deployable as metadata, better for packaging and migrations.

Why not C (Named Credentials and Protected Custom Settings)?

While Named Credentials are ideal, pairing with Protected Custom Settings is valid but suboptimal. Salesforce documentation and Trailhead modules favor Protected Custom Metadata Types over Custom Settings for secret storage due to better deployability, caching, and metadata API support.

This aligns with Salesforce Trailhead ('Securely Store Secrets with Salesforce Features') and secure coding guidelines, emphasizing Named Credentials for callouts and Protected Custom Metadata for high-security secret storage in packages. For unmanaged code vulnerabilities, migrating to these mechanisms (ideally with packaging) prevents exposure.

Answer: B

Explanation:

When integrating high-security back-office systems like an Enterprise Billing System (EBS) and a Document Management System (DMS) with Salesforce, the primary concern for an Integration Architect is maintaining the integrity of the organization's existing security perimeter. In an enterprise landscape with over 10 million customers, these systems are typically governed by strict regulatory and compliance standards (such as PCI-DSS or GDPR) that dictate who can view financial records.

The consultant must consider Enterprise security needs for access to these systems rather than simply attempting to synchronize credentials. This involves evaluating an Identity Federation strategy using protocols like SAML 2.0 or OpenID Connect. Instead of maintaining a separate silo of authentication details within Salesforce (which creates a security risk and administrative overhead), Salesforce should act as a Service Provider (SP) that trusts a central Identity Provider (IdP).1234

Furthermore, the 'seamle5ss access' requirement implies that once a support agent is authenticated into Salesforce, their identity should be propagated to the EBS and DMS to authorize the specific 6view of a7 customer's bill. This is often achieved through Single Sign-On (SSO) and Token-Based Authentication8. By prioritizing the enterprise security framewo9rk, the architect ensures that access is auditable, centralized, and compliant with corporate policies, while providing th10e '360-degree' view required by support agents without forcing them to log in to multiple disconnected systems. Migrating such massive systems (Option A) into Salesforce is technically and financially unfeasible for most enterprises due to data volume and specialized processing logic.

Answer: A

Explanation:

In this scenario, the architecture involves a Remote-Call-In pattern or Batch Synchronization, where an external system (the middleware or ETL tool) initiates communication with Salesforce to update records. For any external system to securely access Salesforce APIs and perform these updates, it must be authenticated and authorized.

The Connected App is the foundational framework that allows an external application to integrate with Salesforce using APIs and standard protocols, such as OAuth 2.0 and SAML. By configuring a Connected App, the architect can define which permissions (Scopes) the middleware has, such as the ability to access data via the REST or Bulk API. This is the correct choice because the middleware needs to 'log in' to Salesforce to push the phone classification data back into the Account or Contact records.

Option B, an API Gateway, is typically used to manage and secure requests going out of an organization to external services, or to provide a facade for on-premise APIs; it does not handle the inbound authentication into Salesforce itself. Option C, Remote Site Settings, is a configuration used solely to permit Salesforce to make outbound calls to a specific external URL (for example, if Salesforce were calling the phone classification service directly via Apex).

Given that the business is flexible with timing (allowing for nightly or 12-hour syncs) and handles 100,000 calls, a Batch Synchronization pattern via an ETL tool is highly efficient. The ETL tool will authenticate against the Connected App using a secure OAuth flow (such as the JWT Bearer Flow for server-to-server integration), retrieve the new phone numbers, call the external classification API, and then bulk-update the Salesforce records. This setup ensures a secure, scalable, and manageable integration that respects Salesforce's security architecture while meeting the high-volume data requirements of the call center.

Answer: B

Explanation:

Prior to implementing Shield Platform Encryption, the most critical step for an Integration Architect is to perform a comprehensive Review of Shield Platform Encryption configurations and their impact on existing platform functionality. Encryption at rest is not a 'set-and-forget' feature; it changes how the Salesforce database interacts with various features, and failing to review these limitations beforehand can lead to significant business disruption.

Salesforce documentation emphasizes that encryption affects several core areas:

SOQL/SOSL Limitations: Encrypted fields have restricted capabilities in WHERE, GROUP BY, and ORDER BY clauses.1 For example, if Social Security Numbers (SSNs) are encrypted using Probabilistic Encryption, they cannot be filtered or sorted in a query.2 This could break existing integrations or reports that rely on finding specific records by SSN.

Search Functionality: While Salesforce supports searching for encrypted data, there are specific behaviors to consider regarding how search indexes are built and updated.

AppExchange and Managed Packages: If the SSN field is used by a third-party app or a managed package, encrypting it might cause those external tools to fail if they are not designed to handle encrypted data types.

Field Attributes: Encrypted fields cannot be used as Unique or External IDs if using the probabilistic scheme, which is a vital consideration for data synchronization architectures.3

Therefore, the architect must first conduct a Business Impact Analysis. This includes identifying where the sensitive data (SSNs) is used in Apex code, Flows, validation rules, and reports. By reviewing the configurations and functional limitations first, the architect can decide between Probabilistic (higher security) and Deterministic (allows filtering) encryption strategies.4 Option A is a step taken during or after implementation (Background Encryption), and Option C is an anti-pattern, as encrypting 'everything' leads to unnecessary performance overhead and massive functional loss. Only after a thorough review can the architect safely proceed with the technical implementation of Shield.

Answer: A

Explanation:

When integrating with a legacy SOAP-only application using a Fire and Forget pattern, Salesforce Outbound Messaging is the native, declarative choice.

Outbound Messaging is a platform feature that sends a SOAP message to a designated endpoint when specific criteria are met. It is inherently asynchronous and provides built-in reliability; if the legacy system is offline, Salesforce will automatically retry the delivery for up to 24 hours. This perfectly fits the 'Fire and Forget' requirement.

For the strongly-typed response back (Remote Call-In), the Enterprise WSDL is the correct recommendation.1415

Enterprise WSDL: This is a strongly-typed WSDL generated specifically for one org's metadata. It includes specific references to16 custom objects and fields, ensu17ring that the legacy system can communicate with Salesforce using a rigid, predictable data structure.

Partner WSDL (Option C): This is a loosely-typed WSDL designed for developers building tools that must work across many different orgs; it is not ideal for an internal, strongly-typed legacy integration.

While Platform Events (Option B) are a modern alternative, they typically use REST or Streaming APIs, making them a less natural fit for an application that 'can only support SOAP'. By combining Outbound Messaging and the Enterprise WSDL, the architect provides a robust, SOAP-native solution that satisfies the business's technical constraints and reliability requirements.