Salesforce Certified Platform Integration Architect free question 2 / 10 · Domain 1: Evaluate the Current System Landscape
A government agency’s back-end services require WS-Security credentials on every request. The team wants to avoid changing the web services and avoid changing how Salesforce invokes them. Which recommended alternative fits?
- Hand-coding WS-Security headers into the outbound SOAP requests using the WSDL2Apex utility and manual XML serialization
- Switching the integration to a callout that sends a username and password in a custom header with one-way SSL
- A security or XML gateway that injects WS-Security credentials into the transaction stream, reusable across Salesforce
- Relying on the session timeout setting, which Salesforce treats as the WS-Security credential for outbound calls
Show the answer and explanation
Answer: C
Why this is correct
The page recommends three alternatives for WS- security protocols. A security or XML gateway injects the WS-Security credentials into the transaction stream, needs no changes to application-level web services or to the invocations from Salesforce, and can be reused. Its cost is extra design, configuration, testing, and maintenance of the injection in the existing gateway approach.
Why the other options are wrong
"Hand-coding WS-Security headers into the outbound SOAP requests using the WSDL2Apex utility and manual XML serialization" … Adding the headers in Salesforce-generated classes changes how Salesforce invokes the services, which the team wants to avoid. It also needs manual XML serialization and more build and test effort.
"Switching the integration to a callout that sends a username and password in a custom header with one-way SSL" … That does not implement WS-Security. The page frames the options around reaching the WS- requirement without changing the services or invocations.
"Relying on the session timeout setting, which Salesforce treats as the WS-Security credential for outbound calls" … A session timeout setting is not a WS-Security credential. The page names three alternatives and this is not one of them.
Where people trip
When the requirement is to change neither the back-end services nor the Salesforce invocations, the gateway is the alternative that meets it.