DATA ARCHITECTURE AND
MANAGEMENT DESIGNER QUESTIONS
WITH COMPLETE ANSWERS
A ddlarge ddretail ddB2C ddcustomer ddwants ddto ddbuild dda dd360 ddview ddof ddits ddcustomer
ddfor ddits ddcall ddcenter ddagents.
The ddcustomer ddinteraction ddis ddcurrently ddmaintained ddin ddthe ddfollowing ddsystem:
1. ddSalesforce ddCRM
2. ddCustom ddbilling ddsolution
3. ddCustomer ddMaster ddData ddmanagement dd(MDM)
4. ddContract ddManagement ddsystem
5. ddMarketing ddsolution
What ddshould dda dddata ddarchitect ddrecommend ddthat ddwould ddhelp ddupgrade
dduniquely ddidentify ddcustomer ddacross
multiple ddsystems:
A. ddStore ddthe ddsalesforce ddid ddin ddall ddthe ddsolutions ddto ddidentify ddthe ddcustomer.
B. ddCreate dda ddcustom ddobject ddthat ddwill ddserve ddas dda ddcross ddreference ddfor ddthe
ddcustomer ddid.
C. ddCreate dda ddcustomer dddata ddbase ddand dduse ddthis ddid ddin ddall ddsystems.
D. ddCreate dda ddcustom ddfield ddas ddexternal ddid ddto ddmaintain ddthe ddcustomer ddId
ddfrom ddthe ddMDM ddsolution. dd- ddAnswer ddD
A ddhealth ddcare ddprovider ddwishes ddto dduse ddsalesforce ddto ddtrack ddpatient ddcare.
ddThe ddfollowing ddactions ddare ddin
Salesforce
1. ddPayment ddProviders: ddOrgas ddwho ddpay ddfor ddthe ddcare dd2 ddpatients.
2. ddDoctors: ddThey ddprovide ddcare ddplan ddfor ddpatients ddand ddneed ddto ddsupport
ddmultiple ddpatients, ddthey ddare
provided ddaccess ddto ddpatient ddinformation.
3. ddPatients: ddThey ddare ddindividuals ddwho ddneed ddcare.
A dddata ddarchitect ddneeds ddto ddmap ddthe ddactor ddto ddSf ddobjects. ddWhat ddshould
ddbe ddthe ddoptimal ddselection ddby ddthe
data ddarchitect?
A. ddPatients ddas ddContacts, ddPayment ddproviders ddas ddAccounts, dd& ddDoctors ddas
ddAccounts
,B. ddPatients ddas ddPerson ddAccounts, ddPayment ddproviders ddas ddAccounts, dd&
ddDoctors ddas ddContacts
C. ddPatients ddas ddPerson ddAccounts, ddPayment ddproviders ddas ddAccounts, dd&
ddDoctors ddas ddPerson ddAccount
D. ddPatients ddas ddAccounts, ddPayment ddproviders ddas ddAccounts, dd& ddDoctors ddas
ddPerson ddAccounts dd- ddAnswer ddC
NTO dd(Northern ddTrail ddOutlets) ddhas dda ddcomplex ddSalesforce ddorg ddwhich ddhas
ddbeen dddeveloped ddover ddpast dd5
years. ddInternal ddusers ddare ddcomplaining ddabt ddmultiple dddata ddissues, ddincluding
ddincomplete ddand ddduplicate
data ddin ddthe ddorg. ddNTO ddhas dddecided ddto ddengage dda dddata ddarchitect ddto
ddanalyze ddand dddefine dddata ddquality
standards.
Which dd3 ddkey ddfactors ddshould dda dddata ddarchitect ddconsider ddwhile dddefining dddata
ddquality ddstandards? ddChoose dd3
answers:
A. ddDefine dddata ddduplication ddstandards ddand ddrules
B. ddDefine ddkey ddfields ddin ddstaging dddatabase ddfor dddata ddcleansing
C. ddMeasure dddata ddtimeliness ddand ddconsistency
D. ddFinalize ddan ddextract ddtransform ddload dd(ETL) ddtool ddfor dddata ddmigration
E. ddMeasure dddata ddcompleteness ddand ddaccuracy dd- ddAnswer ddA,C,E
Universal ddContainers dd(UC) ddrequires dd2 ddyears ddof ddcustomer ddrelated ddcases ddto
ddbe ddavailable ddon ddSF ddfor
operational ddreporting. ddAny ddcases ddolder ddthan dd2 ddyears ddand ddupto dd7 ddyears
ddneed ddto ddbe ddavailable ddon dddemand
to ddthe ddService ddagents. ddUC ddcreates dd5 ddmillion ddcases ddper ddyr.
Which dd2 dddata ddarchiving ddstrategies ddshould dda dddata ddarchitect ddrecommend?
ddChoose dd2 ddoptions:
a. ddUse ddcustom ddobjects ddfor ddcases ddolder ddthan dd2 ddyears ddand dduse ddnightly
ddbatch ddto ddmove ddthem.
b. ddSync ddcases ddolder ddthan dd2 ddyears ddto ddan ddexternal dddatabase, ddand ddprovide
ddaccess ddto ddService ddagents
to ddthe dddatabase
c. ddUse ddBig ddobjects ddfor ddcases ddolder ddthan dd2 ddyears, ddand dduse ddnightly
ddbatch ddto ddmove ddthem.
d. ddUse ddHeroku ddand ddexternal ddobjects ddto dddisplay ddcases ddolder ddthan dd2
ddyears ddand ddbulk ddAPI ddto ddhard
delete ddfrom ddSalesforce. dd- ddAnswer ddC,D
NTO ddwould ddlike ddto ddretrieve ddtheir ddSF ddorgs ddmeta dddata ddprogrammatically ddfor
ddbackup ddwithin dda ddvarious
external. ddWhich ddAPI ddis ddthe ddbest ddfit ddfor ddaccomplishing ddthis ddtask?
, A. ddMetadata ddAPI
B. ddTooling ddAPI
C. ddBulk ddAPI ddin ddserial ddmode
D. ddSOAP ddAPI dd- ddAnswer ddA
A ddcustomer ddis ddoperating ddin dda ddhighly ddreputated ddindustry ddand ddis ddplanning
ddto ddimplement ddSF. ddThe
customer ddinformation ddmaintained ddin ddSF, ddincludes ddthe ddfollowing:
1. ddPersonally, ddidentifiable ddinformation dd(PII)
2. ddIP ddrestrictions ddon ddprofiles ddorganized ddby ddGeographic ddlocation
3. ddFinancial ddrecords ddthat ddneed ddto ddbe ddprivate ddand ddaccessible ddonly ddby ddthe
ddassigned ddSales ddassociate.
4. ddUser ddshould ddnot ddbe ddallowed ddto ddexport ddinformation ddfrom ddSalesforce.
Enterprise ddsecurity ddhas ddmandate ddaccess ddto ddbe ddrestricted ddto ddusers ddwithin
dda ddspecific ddgeography ddand
detail ddmonitoring ddof dduser ddactivity. ddWhich dd3 ddSalesforce ddshield ddcapabilities
ddshould dda dddata ddarchitect
recommend? ddChoose dd3 ddanswers:
A. ddEvent ddmonitoring ddto ddmonitor ddall dduser ddactivities
B. ddRestrict ddaccess ddto ddSF ddfrom ddusers ddoutside ddspecific ddgeography
C. ddPrevent ddSales ddusers ddaccess ddto ddcustomer ddPII ddinformation
D. ddTransaction ddsecurity ddpolicies ddto ddprevent ddexport ddof ddSF ddData.
E. ddEncrypt ddSensitive ddCustomer ddinforma dd- ddAnswer ddA,D,E
To ddaddress dddifferent ddcompliance ddrequirements, ddsuch ddas ddgeneral dddata
ddprotection ddregulation
(GDPR), ddpersonally ddidentifiable ddinformation dd(PII), ddof ddhealth ddinsurance
ddPortability ddand ddAccountability
Act dd(HIPPA) ddand ddothers, dda ddSF ddcustomer dddecided ddto ddcategorize ddeach
dddata ddelement ddin ddSF ddwith ddthe
following:
1. ddData ddowner
2. ddSecurity ddLevel, ddsuch ddas ddconfidential
3. ddCompliance ddtypes ddsuch ddas ddGDPR, ddPII, ddHIPPA
A ddcompliance ddaudit ddwould ddrequire ddSF ddadmins ddto ddgenerate ddreports ddto
ddmanage ddcompliance.
What ddshould dda dddata ddarchitect ddrecommend ddto ddaddress ddthis ddrequirement?
A. ddUse ddmetadata ddAPI, ddto ddextract ddfield ddattribute ddinformation ddand dduse ddthe
ddextract ddto ddclassify ddand
build ddreports
B. ddUse ddfield ddmetadata ddattributes ddfor ddcompliance ddcategorization, dddata ddowner,
ddand dddata
sensitivity ddlevel.
MANAGEMENT DESIGNER QUESTIONS
WITH COMPLETE ANSWERS
A ddlarge ddretail ddB2C ddcustomer ddwants ddto ddbuild dda dd360 ddview ddof ddits ddcustomer
ddfor ddits ddcall ddcenter ddagents.
The ddcustomer ddinteraction ddis ddcurrently ddmaintained ddin ddthe ddfollowing ddsystem:
1. ddSalesforce ddCRM
2. ddCustom ddbilling ddsolution
3. ddCustomer ddMaster ddData ddmanagement dd(MDM)
4. ddContract ddManagement ddsystem
5. ddMarketing ddsolution
What ddshould dda dddata ddarchitect ddrecommend ddthat ddwould ddhelp ddupgrade
dduniquely ddidentify ddcustomer ddacross
multiple ddsystems:
A. ddStore ddthe ddsalesforce ddid ddin ddall ddthe ddsolutions ddto ddidentify ddthe ddcustomer.
B. ddCreate dda ddcustom ddobject ddthat ddwill ddserve ddas dda ddcross ddreference ddfor ddthe
ddcustomer ddid.
C. ddCreate dda ddcustomer dddata ddbase ddand dduse ddthis ddid ddin ddall ddsystems.
D. ddCreate dda ddcustom ddfield ddas ddexternal ddid ddto ddmaintain ddthe ddcustomer ddId
ddfrom ddthe ddMDM ddsolution. dd- ddAnswer ddD
A ddhealth ddcare ddprovider ddwishes ddto dduse ddsalesforce ddto ddtrack ddpatient ddcare.
ddThe ddfollowing ddactions ddare ddin
Salesforce
1. ddPayment ddProviders: ddOrgas ddwho ddpay ddfor ddthe ddcare dd2 ddpatients.
2. ddDoctors: ddThey ddprovide ddcare ddplan ddfor ddpatients ddand ddneed ddto ddsupport
ddmultiple ddpatients, ddthey ddare
provided ddaccess ddto ddpatient ddinformation.
3. ddPatients: ddThey ddare ddindividuals ddwho ddneed ddcare.
A dddata ddarchitect ddneeds ddto ddmap ddthe ddactor ddto ddSf ddobjects. ddWhat ddshould
ddbe ddthe ddoptimal ddselection ddby ddthe
data ddarchitect?
A. ddPatients ddas ddContacts, ddPayment ddproviders ddas ddAccounts, dd& ddDoctors ddas
ddAccounts
,B. ddPatients ddas ddPerson ddAccounts, ddPayment ddproviders ddas ddAccounts, dd&
ddDoctors ddas ddContacts
C. ddPatients ddas ddPerson ddAccounts, ddPayment ddproviders ddas ddAccounts, dd&
ddDoctors ddas ddPerson ddAccount
D. ddPatients ddas ddAccounts, ddPayment ddproviders ddas ddAccounts, dd& ddDoctors ddas
ddPerson ddAccounts dd- ddAnswer ddC
NTO dd(Northern ddTrail ddOutlets) ddhas dda ddcomplex ddSalesforce ddorg ddwhich ddhas
ddbeen dddeveloped ddover ddpast dd5
years. ddInternal ddusers ddare ddcomplaining ddabt ddmultiple dddata ddissues, ddincluding
ddincomplete ddand ddduplicate
data ddin ddthe ddorg. ddNTO ddhas dddecided ddto ddengage dda dddata ddarchitect ddto
ddanalyze ddand dddefine dddata ddquality
standards.
Which dd3 ddkey ddfactors ddshould dda dddata ddarchitect ddconsider ddwhile dddefining dddata
ddquality ddstandards? ddChoose dd3
answers:
A. ddDefine dddata ddduplication ddstandards ddand ddrules
B. ddDefine ddkey ddfields ddin ddstaging dddatabase ddfor dddata ddcleansing
C. ddMeasure dddata ddtimeliness ddand ddconsistency
D. ddFinalize ddan ddextract ddtransform ddload dd(ETL) ddtool ddfor dddata ddmigration
E. ddMeasure dddata ddcompleteness ddand ddaccuracy dd- ddAnswer ddA,C,E
Universal ddContainers dd(UC) ddrequires dd2 ddyears ddof ddcustomer ddrelated ddcases ddto
ddbe ddavailable ddon ddSF ddfor
operational ddreporting. ddAny ddcases ddolder ddthan dd2 ddyears ddand ddupto dd7 ddyears
ddneed ddto ddbe ddavailable ddon dddemand
to ddthe ddService ddagents. ddUC ddcreates dd5 ddmillion ddcases ddper ddyr.
Which dd2 dddata ddarchiving ddstrategies ddshould dda dddata ddarchitect ddrecommend?
ddChoose dd2 ddoptions:
a. ddUse ddcustom ddobjects ddfor ddcases ddolder ddthan dd2 ddyears ddand dduse ddnightly
ddbatch ddto ddmove ddthem.
b. ddSync ddcases ddolder ddthan dd2 ddyears ddto ddan ddexternal dddatabase, ddand ddprovide
ddaccess ddto ddService ddagents
to ddthe dddatabase
c. ddUse ddBig ddobjects ddfor ddcases ddolder ddthan dd2 ddyears, ddand dduse ddnightly
ddbatch ddto ddmove ddthem.
d. ddUse ddHeroku ddand ddexternal ddobjects ddto dddisplay ddcases ddolder ddthan dd2
ddyears ddand ddbulk ddAPI ddto ddhard
delete ddfrom ddSalesforce. dd- ddAnswer ddC,D
NTO ddwould ddlike ddto ddretrieve ddtheir ddSF ddorgs ddmeta dddata ddprogrammatically ddfor
ddbackup ddwithin dda ddvarious
external. ddWhich ddAPI ddis ddthe ddbest ddfit ddfor ddaccomplishing ddthis ddtask?
, A. ddMetadata ddAPI
B. ddTooling ddAPI
C. ddBulk ddAPI ddin ddserial ddmode
D. ddSOAP ddAPI dd- ddAnswer ddA
A ddcustomer ddis ddoperating ddin dda ddhighly ddreputated ddindustry ddand ddis ddplanning
ddto ddimplement ddSF. ddThe
customer ddinformation ddmaintained ddin ddSF, ddincludes ddthe ddfollowing:
1. ddPersonally, ddidentifiable ddinformation dd(PII)
2. ddIP ddrestrictions ddon ddprofiles ddorganized ddby ddGeographic ddlocation
3. ddFinancial ddrecords ddthat ddneed ddto ddbe ddprivate ddand ddaccessible ddonly ddby ddthe
ddassigned ddSales ddassociate.
4. ddUser ddshould ddnot ddbe ddallowed ddto ddexport ddinformation ddfrom ddSalesforce.
Enterprise ddsecurity ddhas ddmandate ddaccess ddto ddbe ddrestricted ddto ddusers ddwithin
dda ddspecific ddgeography ddand
detail ddmonitoring ddof dduser ddactivity. ddWhich dd3 ddSalesforce ddshield ddcapabilities
ddshould dda dddata ddarchitect
recommend? ddChoose dd3 ddanswers:
A. ddEvent ddmonitoring ddto ddmonitor ddall dduser ddactivities
B. ddRestrict ddaccess ddto ddSF ddfrom ddusers ddoutside ddspecific ddgeography
C. ddPrevent ddSales ddusers ddaccess ddto ddcustomer ddPII ddinformation
D. ddTransaction ddsecurity ddpolicies ddto ddprevent ddexport ddof ddSF ddData.
E. ddEncrypt ddSensitive ddCustomer ddinforma dd- ddAnswer ddA,D,E
To ddaddress dddifferent ddcompliance ddrequirements, ddsuch ddas ddgeneral dddata
ddprotection ddregulation
(GDPR), ddpersonally ddidentifiable ddinformation dd(PII), ddof ddhealth ddinsurance
ddPortability ddand ddAccountability
Act dd(HIPPA) ddand ddothers, dda ddSF ddcustomer dddecided ddto ddcategorize ddeach
dddata ddelement ddin ddSF ddwith ddthe
following:
1. ddData ddowner
2. ddSecurity ddLevel, ddsuch ddas ddconfidential
3. ddCompliance ddtypes ddsuch ddas ddGDPR, ddPII, ddHIPPA
A ddcompliance ddaudit ddwould ddrequire ddSF ddadmins ddto ddgenerate ddreports ddto
ddmanage ddcompliance.
What ddshould dda dddata ddarchitect ddrecommend ddto ddaddress ddthis ddrequirement?
A. ddUse ddmetadata ddAPI, ddto ddextract ddfield ddattribute ddinformation ddand dduse ddthe
ddextract ddto ddclassify ddand
build ddreports
B. ddUse ddfield ddmetadata ddattributes ddfor ddcompliance ddcategorization, dddata ddowner,
ddand dddata
sensitivity ddlevel.
