Valid Integration-Architect Dumps shared by ExamDiscuss.com for Helping Passing Integration-Architect Exam! ExamDiscuss.com now offer the newest Integration-Architect exam dumps, the ExamDiscuss.com Integration-Architect exam questions have been updated and answers have been corrected get the newest ExamDiscuss.com Integration-Architect dumps with Test Engine here:
An Integration Architect has designed a mobile application for Salesforce users to get data while on the road using a custom UI. The application is secured with oAuth and is currently functioning well. There is a new requirement where the mobile application needs to obtain the GPS coordinates and storeit on a custom geolocation field. The geolocation field is secured with Field Level Security, so users can view the value without changing it. What should be done to meet the requirement?
Correct Answer: C
Explanation The mobile device should make a REST Apex inbound call to meet the requirement. A REST Apex inbound call allows the mobile device to invoke custom Apex logic on Salesforce using a RESTful interface. The Apex logic can then access the geolocation field using the user's OAuth token and update it with the GPS coordinates from the mobile device. The geolocation field is secured with Field Level Security, so the user can view the value without changing it. A SOAP API inbound call or a REST API inbound call would not be able to access the custom geolocation field, as they are not supported by the standard Salesforce objects and fields. Reference: Salesforce Integration Architecture Designer Resource Guide, page 20
Recent Comments (The most recent comments are at the top.)
Sky - Jun 14, 2025
Answer is: The mobile device makes a REST Apex inbound call.
Rest API respects FLS Rest APEX allows you to bypass the FLS
HM - May 06, 2024
Should be C to invoke Apex logic to update the field.
Recent Comments (The most recent comments are at the top.)
Answer is: The mobile device makes a REST Apex inbound call.
Rest API respects FLS
Rest APEX allows you to bypass the FLS
Should be C to invoke Apex logic to update the field.
https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/compound_fields_geolocation.htm#:~:text=Geolocation%20fields%20are%20accessible%20in,compound%20field%20of%20type%20Location.
Seems to be B. geolocation filed is supported by standard API