To meet the requirement of not having any custom development in Salesforce and to update the opportunities on existing accounts with product usage statistics from an on-premise system, the Integration Architect should consider the following steps:

B. Generate a partner WSDL in Salesforce and provide it to the remote system to create a client stub.

Partner WSDL is typically used for contract-first integrations and allows external systems to generate client stubs for communication with Salesforce. This aligns with the requirement of not having custom development in Salesforce.
C. Create a Workflow outbound message during Opportunity creation and provide the Opportunity ID and Session ID to the remote system.

Workflow outbound messages can be configured in Salesforce to trigger external systems when specific events occur, such as Opportunity creation, and pass relevant data (e.g., Opportunity ID) to the remote system. This approach is a no-code solution and aligns with the requirement.
E. Create a Process Builder outbound message during Opportunity creation and provide the Opportunity ID and Session ID to the remote system.

Similar to Workflow outbound messages, Process Builder can be used to trigger external systems and pass data (e.g., Opportunity ID) during Opportunity creation. This is a no-code approach that aligns with the no custom development requirement.
Options A and D involve callback methods (REST API and SOAP API) that might require custom development or Apex code, which goes against the requirement of not having custom development in Salesforce.






You are correct; Option B and Option D have similarities in the sense that both involve generating a WSDL and using it to facilitate integration. However, there is a difference between the two:

Option B: Generating a partner WSDL in Salesforce and providing it to the remote system is often used for outbound integrations, where external systems consume data or services from Salesforce. This is typically ...

Vinh Hua, true, you rock!

The key words here is "three steps". It mean that we should select one solution with 3 steps to implement.
So A&D can not be selected at the same time.
B&D should be selected together because we can only use SOAP API with WSDL.
=> B&D&C are correct. A is the correct statement also but it is another solution.

BCD is correct.
We can not use SOAP API with out WSDL

ACD

Option B, generating a partner WSDL in Salesforce, is not a recommended approach in this scenario because it requires custom development in Salesforce. The requirement is that UC does not want any custom development in Salesforce.

while Options A using a REST API callback, is recommended approaches for updating the Opportunity record with the product usage data from the remote system without custom development in Salesforce.