Module: Salesforce & Heroku Integration “Answers”

I)A replicated data set offloads processing and requests from an origin data server.
II)A replicated data set is always and immediately in sync with the origin data.
III)A replicated data set reduces data access latency.
IV)A replicated data set supports bidirectional writes.
[bg_collapse view=”button-orange” color=”#4a4949″ expand_text=”Show Answers” collapse_text=”Close Answer” ]
II)A replicated data set is always and immediately in sync with the origin data.
[/bg_collapse]

I)OData 2.0 and 4.0
II)REST with JSON payloads
III)REST with XML payloads
IV)SOAP
V)All of the above
[bg_collapse view=”button-orange” color=”#4a4949″ expand_text=”Show Answers” collapse_text=”Close Answer” ]
V)All of the above
[/bg_collapse]

I)Pre-shared keys
II)Basic usernames and passwords
III)OAuth
IV)SAML
[bg_collapse view=”button-orange” color=”#4a4949″ expand_text=”Show Answers” collapse_text=”Close Answer” ]
III)OAuth
[/bg_collapse]

I)Web sockets
II)Apex triggers or outbound messages
III)Message bus
IV)Corba
[bg_collapse view=”button-orange” color=”#4a4949″ expand_text=”Show Answers” collapse_text=”Close Answer” ]
II)Apex triggers or outbound messages
[/bg_collapse]

I)One-way data replication
II)Bidirectional data replication
III)Data proxy with Salesforce Connect
IV)All of the above
[bg_collapse view=”button-orange” color=”#4a4949″ expand_text=”Show Answers” collapse_text=”Close Answer” ]
IV)All of the above
[/bg_collapse]

I)A single integration user’s credentials are stored.
II)OAuth provides Heroku Connect with API tokens after the user authorizes the Heroku Connect application on Salesforce.
III)SAML authorizes Heroku Connect to make API calls.
IV)The end user of a Heroku app authorizes Heroku Connect via OAuth.
[bg_collapse view=”button-orange” color=”#4a4949″ expand_text=”Show Answers” collapse_text=”Close Answer” ]
II)OAuth provides Heroku Connect with API tokens after the user authorizes the Heroku Connect application on Salesforce.
[/bg_collapse]

I)Instantly in both directions
II)Near real time in both directions
III)Near real time for writes to Salesforce, and on a 30-second polling window for writes to Heroku Postgres
IV)Near real time for writes to Salesforce, and either on a polling window or near real time for writes to Heroku Postgres (depending on the user configuration)
[bg_collapse view=”button-orange” color=”#4a4949″ expand_text=”Show Answers” collapse_text=”Close Answer” ]
IV)Near real time for writes to Salesforce, and either on a polling window or near real time for writes to Heroku Postgres (depending on the user configuration)
[/bg_collapse]

I)Developing ETL services
II)Replicating external data into Salesforce
III)Proxying external data into Salesforce
IV)Bidirectional syncing of external data in Salesforce
[bg_collapse view=”button-orange” color=”#4a4949″ expand_text=”Show Answers” collapse_text=”Close Answer” ]
III)Proxying external data into Salesforce
[/bg_collapse]

I)Cross-object relationships
II)Data paging
III)Search
IV)All of the above
[bg_collapse view=”button-orange” color=”#4a4949″ expand_text=”Show Answers” collapse_text=”Close Answer” ]
IV)All of the above
[/bg_collapse]

I)The data is always fetched on demand.
II)If the origin is offline, the data is still available via Salesforce Connect.
III)Standard protocols like OData can easily proxy external data into Salesforce.
IV)Data security can be enforced using per-user or per-application authentication.
[bg_collapse view=”button-orange” color=”#4a4949″ expand_text=”Show Answers” collapse_text=”Close Answer” ]
II)If the origin is offline, the data is still available via Salesforce Connect.
[/bg_collapse]

I)Anonymous access without credentials on trusted networks
II)Username and password with an OAuth connected app
III)OAuth web or user-agent flow in which the user authorizes a connected app using browser redirects
IV)B and C
V)A and C
[bg_collapse view=”button-orange” color=”#4a4949″ expand_text=”Show Answers” collapse_text=”Close Answer” ]
IV)B and C
[/bg_collapse]

I)Insert or update records
II)Execute processes as another user
III)Access database log files
IV)Feed your kitten
[bg_collapse view=”button-orange” color=”#4a4949″ expand_text=”Show Answers” collapse_text=”Close Answer” ]
I)Insert or update records
[/bg_collapse]

I)The message can deliver the payload only as SOAP.
II)The message supports different authentication mechanisms.
III)Messages are completely declarative.
IV)The message can handle every database event.
[bg_collapse view=”button-orange” color=”#4a4949″ expand_text=”Show Answers” collapse_text=”Close Answer” ]
III)Messages are completely declarative.
[/bg_collapse]

I)Pre-shared keys
II)Username and password credentials
III)OAuth flows using named credentials in the Remote Site settings
IV)All of the above
[bg_collapse view=”button-orange” color=”#4a4949″ expand_text=”Show Answers” collapse_text=”Close Answer” ]
IV)All of the above
[/bg_collapse]

I)Node.js / JavaScript
II)Java, Scala, Clojure
III)Python
IV)PHP
V)All of the above
[bg_collapse view=”button-orange” color=”#4a4949″ expand_text=”Show Answers” collapse_text=”Close Answer” ]
V)All of the above
[/bg_collapse]

I)Username and password
II)OAuth
III)Signed request
IV)Either OAuth or signed request
[bg_collapse view=”button-orange” color=”#4a4949″ expand_text=”Show Answers” collapse_text=”Close Answer” ]
IV)Either OAuth or signed request
[/bg_collapse]

I)Node.js / JavaScript
II)Java, Scala, Clojure
III)Python
IV)PHP
V)All of the above
[bg_collapse view=”button-orange” color=”#4a4949″ expand_text=”Show Answers” collapse_text=”Close Answer” ]
V)All of the above
[/bg_collapse]

I)Display real estate photos in Salesforce for house listings
II)Render custom widgets on Chatter feeds
III)Display third-party apps in Salesforce
IV)All of the above
[bg_collapse view=”button-orange” color=”#4a4949″ expand_text=”Show Answers” collapse_text=”Close Answer” ]
IV)All of the above
[/bg_collapse]