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

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.

Digitally sign the Payload using aprivate key trusted by the external system.

Include a secret passphrase in the payload that is a validated by the external system.

Base64 encode the data to ensure untrusted 3rd parties don't see it.

Utilize a 3rd-party SSO solution to authenticate the session.

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.

Apex callout

Visualforce

Custom Web tab

Lightning connect

Implement a Regression Testing policy to catch issues earlier in the development process.

Use a requirements traceability matrix to track data model changes back to the requirement that prompted them.

Implement a continuous Integration process to identify issues earlier in the development process.

Encourage code developers and integration developers to work in separate sandboxes.

Use a publisher action to update the data and callback to the other system.

Use the generic streaming API to publish changes and listen for updates.

Use the SOAP API to upsert the data. The API will then return all opportunity details.

Use a custom Apex class with a webservice method that performs both actions.

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.

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.

Create a new text field to contain a hashed value for (first name+last name + street number) in Universal containers org and define it as External ID.

Create an indexed formula field for (first name+last name + street number) so that a search can be done on the key before loading records.

Createa new formula field for (first name+last name + street number) in universal containers org and use it as External ID.

Create no new fields, but define the three fields (first name+last name + street number) as External IDs in universal Containers org.

Too many callouts resulting in exceeding the daily limit for number of callouts.

Code changesmay be required following upgrades to the ERP system.

DML operations are not allowed right after Apex callouts.

Appropriate error handling to retry failed messages.

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.

The trigger is failing Unit Tests that access the new data.

API limits being limited.

Data skew is causing record locking issues on the Oder Share object.

Record locking contention on the parent Account.

Utilize named credentials to store the username/password of the web service end post.

Utilize a custom object with an encrypted text field to store the username/password of the web service end point.

Utilize protected custom settings to store the username/password of the web service end point.

Store the username/password directly in the Apex class that will be obfuscated in the managed package.

Use Salesforce-to- Salesforce to keep data synchronized between production and full sandboxes.

Utilize a middleware solution and batch API to do a nightly synch from production to Full sandbox.

Create APEX unit tests so testing can be done against Production data, but rolled back before being committed.

Request that Salesforce to schedule a full sandbox refresh on a nightly basis.

External IDs must be Text fields

External IDs are always searchable

External IDs fields are always unique

External IDs can be used to upsert records

Outbound messaging

APEX Batch

APEX Callout

Middleware

Refresh a Full Sandbox.

Use the metadata API.

Request a Snapshot from Support

Refresh a Copy Sandbox.

use the Apex Data Loader.

VPN

Two-way SSL

Profile Security

IP Whitelisting

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.

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

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.

Base64 encode the data before performing the call out from Apex.

Encrypt the data with a shared key before performing the Apex callout.

Use platform Encryption to secure the data before transporting.

Salesforce automatically secures all data transmissions to external systems.