Mobile-Solutions-Architecture-Designer Salesforce Certified Mobile Solutions Architecture Designer Questions and Answers

Canvas can provide authorization information via the signed Request.

The canvas SDK can be used to make an external systems UI look like Salesforce.

Canvas can send data to an external system asynchronously.

Canvas endpoint URLs can be dynamically changed via a Lifecycle Handler.

Write a nightly batch job to send customer information to ERP.

Write a visualforce page to send order information to ERP.

Writean opportunity trigger to send order information to ERP.

Write an outbound message to send order information to ERP.

Maximum number of External IDs allowed on an objecthas been reached,

Maximum number of fields of an object has been reached.

Maximum number of skinny tables has been reached.

Maximum number of indexes allowed on an object has been reached.

Refresh a Full Sandbox.

Use the metadata API.

Request a Snapshot from Support

Refresh a Copy Sandbox.

use the Apex Data Loader.

DML limits on Bulk are not governed on Salesforce servers.

The SOAP API provides jpb monitoring on the Salesforce setup menu.

The Bulk API allows multiple attachments to be leaded from within a single ZIP file.

The SOAP API avoids record locking contention on parent objects of Master-Details relationship.

The Bulk API may cause record locking contension on parent objects od Master-Details relationship.

Utilize the enterprise WSDL to query Salesforce from the Accounting system for opportunities that have changed to Closed-Won.

Utilize an Enterprise Service Bus to the web service calls between Salesforce and the accounting System.

Utilize workflow outbound messaging, which has a built-in queuing framework.

Utilize an Apex trigger with an @future class to callout to the accounting system after the month-end processing is complete.

Utilize the Enterprise WSDL login() operation to obtain a new session ID.

Utilize an oAuth Username-Password flow to obtain a new oAuth token for the session ID.

Utilize the REST API login() operation to obtain a new session ID

Utilize the session ID contained within the outbound message notification as theauthorization header.

Utilize the partner WSDL with oAuth to obtain a valid oAuth token for the session ID.

Write a Batch Apex class to manage the deduplication

Assign new contacts to queues to be reviewed by a data quality team.

Leverage an AppExchange data management toolto de-duplicate contacts.

Enable duplicate management in the org to prevent duplicates.

Implement a VisualForce page that validates entered addresses against an API.

Write a trigger with an @future callout that validates addresses against an API.

Build a custom Address object and a trigger that will validate the address against the object.

Leverage an Appexchange application to validate addresses entered.

Use custom Linksto direct users to the appropriate ERP system to vieworder status.

Build all Integrations as nightly ETL batches to minimize real-time overhead.

Leverage Apex callouts to integrate directly with acquired applications.

Use an ESB to abstract the Salesforce integration from other enterprise applications.

Leverage a time-based workflow action to trigger an accountoutbound message notification for all records updated within the last 24 hours.

Leverage the Enterprise WSDL getUpdated() operation to retrieve Account records updated within the last 24 hours.

Leverage the Salesforce Data Replication API getUpdated() operation to retrieve Accounts records updated within the last 24 hours.

Leverage a third party tool ETL with a dynamic changing SOQL to retrieve Accounts updated within the last 24 hours.

Leverage the REST API / sObjects / Account / updated URI to retrieve Accounts records updated within the last 24 hours.

Ask the ERP report designers to redesign the report to provide properly formatted data.

Implements a regression testing policy to detect issues following development.

Use SOAP headers to turn off validation rules and triggers during the integration.

Review the Salesforce data model and Validation rules and modify the integration as necessary.

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.

Utilize a single " Integration User " with the " Modify All data " profile setting enabled so thatall integrations always have access to all data.

Utilize separate credentials and profiles for each integration, one having " view All " to ties and the other having " Modify All " to Accounts.

Use a single " Integration User " with profile settings restricted to " view All " for opportunity and " Modify All " for Accounts.

Utilize separate credentials for each system with both credentials having the " modify all data " permission on the profile.

Too many concurrent sessions

Reaching an API call limit.

Reaching a logins per Day limit.

Too many record-lock errors

Write to OData - Compliant data sources without APEX.

Read from OData - Compliant data sources without APEX.

Associate external object records to Salesforce Account records.

Write triggers and workflows on external objects.

Write SOQL queries on external object.

Web-to-Lead requests have their own limits separate from other APIs.

Web-to-Lead is a simple way to capture responses to marketing landingpages.

Web-to-Lead can be utilized for Lead data migrations.

web-to-Lead can be used to de-duplicate leads during integrations.

SMTP

TLS

SSH

SFTP

Write a custom Apex web service, Which will be called from the marketing system to retrieve customer data.

Use Apex callout to send customer data from Salesforce to the marketing system

Use a middleware tool to pull customer data from Salesforce and push it to the marketing system on adaily basis.

Builda custom java application using the Enterprise WSDL to pull data from Salesforce and push it to the marketing system.

Use outbound messages to send customer data from Salesforce to the marketing system.

Outbound message to MDM with a callback to Salesforce to mark duplicate Leads.

Sync the MDM system to a custom object in Salesforce and execute a Lookup validation rule against the object.

Batch APEX process to de-duplicate all records first in Salesforce then against MDM, deleting the newest MDM record.

Use Out-of-the-Box Lead De-duplication Rules to checkagainst MDM.

Use oAuth to authorize the portal to access the chatter API on behalf of the user.

Use oAuth Which will pass their portal credentials to the chatter API.

Use a chatter API integrationuser which authenticates to salesforce using oAuth.

Use a chatter API integration user which authenticatesto Salesforce using Enterprise WSDL login().

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.