Adobe AD0-E600 Exam Questions Instant Access

Question 1

When sending data through the RESTful API. how can data engineers make sure the payload being sent is formatted property in real time?

ALeveraging asynchronous validation, data engineers can review error messages for records that fail validation.

BLeveraging synchronous validation, data engineers can review error messages for records that fail validation.

CAs long as the data matches the pre-defined SXM schema, records in the payload pass

DAll data is ingested and query services reporting identify any records that do not pass custom validation rules.

Answer : B

When sending data through the RESTful API, data engineers can make sure the payload being sent is formatted properly in real time by leveraging synchronous validation. Synchronous validation allows data engineers to review error messages for records that fail validation

Question 2

A data architect responsible for maintaining existing schemas is notified that a previously defined mandatory field is no longer available due to some changes in the inbound dat

a. The data architect confirms the existing schema has been saved and is currently being leveraged in data ingestion.

Which option does the data architect have?

ARemove the previously defined field

BMake the current mandatory field optional

CRename the existing field

DAssign the field a new data type

Answer : B

If a previously defined mandatory field is no longer available due to some changes in the inbound data, the data architect responsible for maintaining existing schemas has the following options:

Remove the previously defined field: This option is not appropriate because the field is mandatory and removing it would cause issues with data ingestion.

Make the current mandatory field optional: This option is appropriate because the field is no longer available and making it optional would allow data ingestion to continue without issues.

Rename the existing field: This option is not appropriate because renaming the field would cause issues with data ingestion.

Assign the field a new data type: This option is not appropriate because the field is mandatory and changing its data type would cause issues with data ingestion.

Therefore, the data architect can make the current mandatory field optional.

Question 3

Given the following segment definition:

personalEmail.3ddress.isNotNull()and homeAddress.city.equalsrChicago", (rue) and homeAddress.statePfovince.equalsCIL". false)

There is a profile that meets the criteria for the segment. Given the following segment job runs:

T1: segment job run (no attribute changes)

T2: segment job run (no attribute changes)

T3: segment job run (homeAddress.crty attribute changed to Oakbrook)

T4: segment job run (personalEmail.address value changes)

What is the segement membership status at each time period?

AExited. Existing. Exited. Realized

BRealized. Existing. Exited. Exited

CExisting. Realized. Exited. Exited

DRealized Exited. Existing. Exited

Answer : C

The segment membership status at each time period is Existing, Realized, Exited, Exited. Reference: https://experienceleague.adobe.com/docs/segmentation/using/segmentation-workflow/segmentation-job-status.html?lang=en#segment-job-status

Question 4

A B2B business (the client) is migrating its data warehouse (DWH) solution to AEP. Currently, they are using what they call Recipient ID as the main identifier to recognize client employees. That Recipient 10 is generated inside the DWH. That solution will not be available once AEP is live, so the solution architect needs to consider potential alternatives.

After working with the client lead and a data engineer, the solution architect identifies that a combination of Company ID and Hashed Employee Email would be a good replacement for the Recipient ID to make it more unique.

How can the solution architect generate that identity within AEP?

AThe Company ID (non-people identifier) must be set up as a primary ID. The Hashed Employee Email as a secondary ID and AEP will automatically reconcile them.

BThe Company ID and Hashed Employee Email must be combined in AEP data prep and passed as a unique primary identity.

CThe Company ID and Hashed Employee Email must be combined outside of AEP and passed as a unique primary identity.

DThe Hashed Employee Email must be set up as a primary ID. The Company ID (non-people identifier) as a secondary ID and AEP will automatically reconcile them.

Answer : C

https://experienceleague.adobe.com/docs/experience-platform/identity/home.html?lang=en

Question 5

A data engineer must set up a Streaming Connection with new authentication via the AEP Ul to stream non XDM data into an existing Dataset. How should the data engineer proceed?

ASources > Streaming > HTTP API > New Account > Add Data > Select Data > Select Dataset > Finish

BSources > Streaming > HTTP API > Add Data > New Account > Select Data > Map Fields to XDM > New Dataset > Finish

CDestination > Streaming > HTTP API > New Account > Select Data > Map Fields to XDM Select Dataset > Finish

DSources > Streaming > HTTP API > Add Data > New Account > Select Data > Map Fields to XDM > Select Dataset > Finish

Answer : D

https://experienceleague.adobe.com/docs/experience-platform/sources/api-tutorials/create/streaming/http.html?lang=en

Question 6

A data engineer creates a custom identity namespace within AEP. However, this custom Identity namespace is the wrong Identity type. What can the data engineer do to update the identity namespace?

ACreate a new custom Identity Namespace with the correct Identity type.

BUsing the Identity Namespace APIs, update the custom Identity type.

CEdit the Identity Namespace type within the AEP User-Interface under Identities.

DDelete the custom Identity Namespace from the AEP User-Interface under Identities.

Answer : A

https://experienceleague.adobe.com/docs/experience-platform/identity/namespaces.html?lang=en

Question 7

A data engineer is ingesting time-series data in CSV format from a CRM system. The source data contains a "subscription" field that contains what level of subscription the customer has purchased.

The data is ingested into a target field called "subscriptionLevel". which is an enum field that accepts the following values: "Lite*. "Standard", and "Pro''.

The data engineer knows that the CSV files contain some rows that do not conform to the above enum. Instead of rejecting those rows, the data engineer wants to transform non-conforming fields to "Standard".

Which mapping function(s) will accomplish this?

Aiif(subscription.equals('Lite') &&subscriptiorvequ3ls('Standard') && sub$ctiption.eqoals('Pro'). subscription. el$e('5tandard'))

Biif(subscription.noiEquals(*Lite' || 'Standard' || 'Pro'), subscription, subscription, replacestrf 'Standard'))

Ciif(subscription.notEquals('Lite') || subscription.notEqualsl 'Standard') || subscription.notEquatsCPro'). 'Standard', subscription)

Diif(subscription.equals('Lite') || subscription.equals('Standard') || subscriptionequalsfPro'). subscription. 'Standard')

Answer : C

you can use Data Prep functions to compute and calculate values based on what is entered in source fields. The iif function returns one value if a condition is true and another value if it is false.

https://experienceleague.adobe.com/docs/experience-platform/data-prep/functions.html?lang=en

Adobe Experience Platform Technical Foundations AD0-E600 Exam Questions