AD0-E605 Question #79: Real Exam Question with Answer & Explanation

An architect for a healthcare organization has been given the following requirements from the organization's compliance and legal team regarding web analytics data collection: 1. The data collected on the organization's home page cannot collect any known identifiers and will not be considered Restricted Healthcare Data (RHD). 2. Once the user authenticates to the website, known identifiers can be collected, but any linked data to the known healthcare identifier will be considered RHD. 3. Onsite personalization can only be done using non-RHD data. Below is a sample web analytics record from the Organization's home page: { "eventType": "web.webpagedetails.pageViews", "_id": "ABC-123", "timestamp": "2023-09-27T15:02:07.977Z", "web": { "webPageDetails": { "name": "Homepage", "siteSection": "Home" } }, "identityMap": { "ECID": [ { "id": "12345678" } ] } } And an example of a web analytics record once a user authenticates: { "eventType": "web.webpagedetails.pageViews", "_id": "ABC-1234", "timestamp": "2023-09-27T15:03:07.977Z", "web": { "webPageDetails": { "name": "Customer Login", "siteSection": "Healthcare Authenticated" } }, "identityMap": { "ECID": [ { "id": "12345678" } ], "CustomerHealthCareID": [ { "id": "ABC" } ] } } Assume that all web analytics data will be enabled for Profile with ECID as the Primary Identity. Given the above requirements and the organization's desire to personalize its website visitor's experience, how would the Platform be configured to accommodate both requirements?