AD0-E605 · Question #41
An engineer has been mandated with ingesting data via the Adobe Edge Network Server API for various data coming from the website. The engineer notices that there seems to be a discrepancy with the Edg
The correct answer is C. Use location hints in their calls. Location hints are the native solution built into the Adobe Edge Network Server API specifically for this scenario. When the first request in a session hits an Edge node, the response includes a location hint - a cluster identifier that the engineer can capture and pass in all su
Question
An engineer has been mandated with ingesting data via the Adobe Edge Network Server API for various data coming from the website. The engineer notices that there seems to be a discrepancy with the Edge profile not qualifying in real-time for various Edge-based personalization use cases. Upon integration, the engineer finds that mid-stream some of the data appears to be routed to a different Edge likely caused by a customer turning on/off a VPN. How best would the engineer resolve this issue to ensure all data is always routed to the same Edge in the initiating session?
Options
- AUse the Web SDK
- BBuild a middleware service to catch and resolve these issues
- CUse location hints in their calls
- DEnable cross-edge synchronization to resolve discrepancies
How the community answered
(38 responses)- A5% (2)
- B16% (6)
- C76% (29)
- D3% (1)
Explanation
Location hints are the native solution built into the Adobe Edge Network Server API specifically for this scenario. When the first request in a session hits an Edge node, the response includes a location hint - a cluster identifier that the engineer can capture and pass in all subsequent API calls, effectively pinning the session to that same Edge node regardless of IP address changes caused by VPN toggling.
A (Web SDK) is wrong because the mandate is to use the Server API; switching to the Web SDK is an architectural change, not a fix, and the Web SDK handles location hints automatically - which is precisely why the Server API exposes them manually for server-side implementations.
B (middleware service) is wrong because it introduces unnecessary complexity and latency to solve a problem the API already handles natively through location hints.
D (cross-edge synchronization) is wrong because this is not a real Adobe Edge Network feature - it's a plausible-sounding distractor. Real-time personalization requires data to be local on the Edge node, not synchronized after the fact.
Memory tip: Think of location hints as a "sticky note" on every API call that says "take this to the same Edge server I started with" - once you grab the hint from the first response, staple it to every subsequent request in the session.
Topics
Community Discussion
No community discussion yet for this question.