Exam 1Y0-403 All QuestionsBrowse all questions from this exam
Go to Exam
Question 52

Scenario: A Citrix Architect is configuring a multi-location profile strategy as part of a large Citrix Virtual Apps and Desktops solution. The architect needs to implement a single policy that sets the profile path for all users and distributes the user profiles between 3 shares and 9 file servers.

✑ New York users: Server: NYC-FS.company.lan `" Share: NYC-Profiles$

✑ Miami users: Server: MIA-FS.company.lan `" Share: MIA-Profiles$

✑ San Francisco users: Server: SFO-FS.company.lan `" Share: SFO-Profiles$

Which value constitutes a valid path for use with a Citrix Profile Management policy?

    Correct Answer: C

    The correct value for a Citrix Profile Management policy must use system variables rather than user environment variables. Option C uses system variables, including #DataCenter#, which corresponds to the defined data center shares (NYC, MIA, SFO). It correctly identifies the structure \#DataCenter#-FS.company.lan\#DataCenter#-Profiles$\#sAMAccountName#\%ProfileVer%\, ensuring profiles are distributed according to the specified servers and shares.

Discussion
cloudaccountOption: C

Correct answer is C. As per https://docs.citrix.com/en-us/profile-management/current-release/plan/multiple-file-servers.html, Do not use user environment variables such as %homeshare% to distinguish profiles or servers. Profile Management recognizes system environment variables but not user environment variables.

Bobo11

Agree; The user profile path can be configured by means of computer specific group policies or system variables.

d0bermannnOption: C

C. \\#DataCenter#-FS.company.lan\#DataCenter#-Profiles$\#sAMAccountName#\%ProfileVer%\ use computer specific group policies or system variables

certhunterfembotOption: C

C "You configure the path to the user store as: \\#l#.userstore.myschools.net\profile\#sAMAccountName#\%ProfileVer%\" https://docs.citrix.com/en-us/profile-management/current-release/plan/multiple-file-servers.html

examrevisionOption: D

It is shared across 9 different file servers so wouldn't #DFSROOT# be viable?