Mobile-Solutions-Architecture-Designer Salesforce Certified Mobile Solutions Architecture Designer(SP23) Questions and Answers

Error reporting is not enabledin Salesforce.

The integration takes more than five minutes to run.

The integration is causing UC to exceedits API limits

The Integration cannot find the parent orders for some Shipments.

user Acceptance Testing

Unit Testing

Regression Testing

Performance testing

SOAP callouts consume API limits.

WSDL2Apex supports RPC-style SOAP callouts.

WSDL2Apex can be used to generate stub code.

SOAP callouts cannot occur after any DML statements.

Load the data into salesforce and then utilize the contact Duplicate Rule feature

Utilize an off-platform de-duplication tool prior to loading.

Create a de-duplication trigger before loading the data.

Utilize a batch apex process to de-duplicate thedata after loading.

Download the latest enterprise WSDL that contains the new object definition to generate Web service stubs for the new Salesforce object.

Download the latest partner WSDL that contains the new object definition to generate web services stubs for the new salesforce object

Migrate to the partner WSDL to generate a generic sObject service stub that can be leveraged for existing and future Salesforce objects

Migrate to the metadata API to download the new salesforce sObject definition into the financial system integration.

Share reports and dashboards between Salesforceorgs.

Automatically publish data from the publisher org.

Manually consume data into the consumer org.

Integrate data between Salesforce orgs via pre-built web service adapters.

Publish data from the publisher's Account object to the consumer'sCustomer__c object.

Configure Login IP Ranges on any profiles used by Integration

Use a login flow to validate the IP and request a 2nd factor if incorrect

Use a trigger to change the user's profile if their IP is not trusted.

Enable the "Lock sessions to the IP address from which they originated" setting.

Create a mobile Integration user ID whose credentialsare stored within the mobile application code.

Prompt for the mobile user's username and Password; utilize the oAuth Username-Password flow to obtain an oAuth token.

Redirect to Salesforce via the User-agent oAuth flow to obtain an access token and refresh token.

Prompt for the mobile user's username and password; utilize the Enterprise WSDL login() operation to obtain a session ID.

Provide a session ID as part of the outbound message.

Repeatedly send a SOAP notification for up to 24 hours until an acknowledgement is received.

Build integration components without the Useof APEX.

Define a WSDL based upon 2 objects related via Master-Detaikls relationship.

Define a custom WSDL based upon an Apex Interface class definition.

Setup CORS to whitelistall domains that the client scripts communicate with.

utilize the canvas SDK to perform the callouts.

Ensure each javascript resource communicates only with its origin.

Set up Remote site settings for all domains that the client scripts communicate with.

Salesforce-to-Salesforce has no built-in support bi-directional(two-way) integrations.

Salesforce-to-Salesforce has a limit on number of records shared between systems.

salesforce-to-Salesforce does not support linking/sharing with existing records in a receiving org.

salesforce-to-Salesforce has no built-in support for objects with Parent-child relationships.

REST API to continuously poll Salesforce for updates to records.

Generic Streaming API to support notifications coming from other systems.

Streaming API to support push notifications to users on mobile devices using Salesforce1.

Utilize ActionPoller to perform an Apex Callout to the external system to retrieve data.

Streaming API to support real-time data updates by other users within Salesforce.

Use an outbound Message with the record's data.

Use lightning connect to save the data to an external object.

Use an Apex class to perform the REST callout asynchronously.

use the REST API with the content-Type headerset to "JSON."

Users should be testingin a Partial Sandbox in order to replicate Production functionality and performance characteristics.

Users should be testing in a Full Sandbox in order to replicate Production functionality and performance characteristics.

Users should be testing with date loaded into the Developer sandbox in order to replication Production functionality and performance, characteristics.

Users should be testing in a Developer Pro sandbox in order to replicate Production functionality and performance characteristics.

Use outbound Messaging to notify Salesforce promptly when product availability changes in the source system.

Store the Salesforce Product ID in the source system to eliminate the needfor External IDs and UPSERT API calls.

Pre-process the data to avoid the need for workflow rules or triggers

Use the Bulk API UPDATE or UPSERT records more efficiently.

Contact Salesforce support to request that they turn off record locking on theProduct2 object.

Use Apex callout to send case status from Salesforce to the legacy system.

use Outbound messages to send status updates from Salesforce to the legacy system.

Use a middleware tool to pull case status from Salesforce and push to the legacy system at regular intervals.

Write an Apex web service returning case status, to be called from the legacy system.

They cannot utilize publisher actions.

They require unit and functional testing

They cannot be built or maintained declaratively

They consume more APIlimits than SOAP or REST API

Utilizelightning connect with custom ApexAdapter to provided CRUD access to the data warehouse

Utilize a canvas application to render the data warehouse data from within Salesforce

Utilize a visual force page from 3rd party JavaScript library that will provide CRUD capabilities to the data warehouse.

Utilize a 3rd party tool from the App-Exchange that will provide CRUD capabilities between the data warehouse and salesforce

Custom Apex class with webservice methods that implement the SMTP protocol.

Custom InboundEmailHandler to process the messages.

Lightning connect with an oData/SMTP interchange.

Custom Apex batch job to check for SMTP messages.

Review the firewall logs to make sure that the outbound messages are being delivered.

Review the Enterprise Service Bus logs to make sure that successful orders arebeing acknowledged

Review at the outbound Messaging Deliverystatus logs to make sure that the messages are being delivered and acknowledged by the target system.

Review the Enterprise Service Bus logs t make sure that orders are being created only one time.

Review at the outbound Messaging Audit logs to make sure that the messages are being successfullyprocessed by the target system.

Workbench

Data Loader

Force.com SOAP Explorer

Metadata audit trail

Leverage the REST API to receive orders from the ERP system as they are created.

Leverage Salesforce Lightning Connect to display order information in Salesforce.

write an outboundmessage to receive orders from ERP system as they are created.

Build a scheduled ETL job to sync all customer order history in the orders object.