MENU
If the Sitecore Content Management instance can be accessed by multiple host names, what would you do to enable users for each site to be able to log in to the Sitecore shell?
Suggested Answer: A
Get Premium Sitecore-10-NET-Developer Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
43 comments · newest first
AN
Angella
11 months ago
Agreed, updating roles is the way to go!
VI
Vilma
11 months ago
Adding AllowedCorsOriginsGroup seems a bit overkill for this.
LA
Launa
11 months ago
Wait, can you really use wild-card options in the Identity Server?
EM
Emogene
11 months ago
I think patching the web.config is a solid approach too.
VE
Velda
12 months ago
Definitely need to update the role for each user group.
BE
Bettina
12 months ago
Adding AllowedCorsOriginsGroup sounds familiar, but I can't recall if that's specifically for enabling logins or something else.
LO
Louann
1 year ago
I’m a bit confused about the Identity Server settings. I think wild-card options could work, but I’m not confident about removing host names.
AN
Angella
1 year ago
I practiced a similar question where we had to manage permissions, and I feel like option B might be the way to go here.
RO
Rodolfo
1 year ago
I think I remember something about updating user roles, but I'm not entirely sure if that's the right approach for multiple host names.
AL
Altha
1 year ago
I'm a bit confused by this question. It seems like we need to make sure the users can access the Sitecore shell for each site, but I'm not sure if that's the same as just updating the roles. Maybe Option A about patching the web.config is the way to go, but I'm not 100% confident in that.
NA
Nathan
1 year ago
Okay, let's think this through step-by-step. If the Sitecore instance can be accessed by multiple host names, we need to make sure the users can log in to the shell for each site. Option C about removing the host names and using wildcards doesn't seem right to me. I'm going to go with Option B and focus on updating the user roles.
TR
Tracey
1 year ago
Hmm, this is a tricky one. I'm not sure if patching the web.config is the best approach, as that could have unintended consequences. I'm leaning towards Option D - adding the AllowedCorsOriginsGroup for each site to the Identity Server configuration.
MA
Marnie
1 year ago
I think the key here is to make sure the users have the right permissions for each site. Option B sounds like the way to go - updating the roles for each user group to include the appropriate site permissions.
CA
Carmelina
1 year ago
Okay, I've got this. LUN migration is used to move LUNs between storage service gateways without disrupting service for cloud consumers. That's got to be the right answer.
JE
Jesusita
1 year ago
I'm a bit confused by this one. The options don't seem to clearly match the question. I'll have to re-read it a few times and see if I can figure out the right answer.
CA
Carmen
1 year ago
I remember studying the delta hedging concepts, the delta of 0.83 seems pretty high, but I'm not sure how to calculate the exact number of calls needed.
AP
Apolonia
1 year ago
I've got a good feeling about this one. The key details are that it's a not-for-profit hospital and makes up 25% of hospitals in the US. Based on that, I'm going to go with A. Government.
JE
Jeanice
1 year ago
I thought the correct answer was to sacrifice a goat to the Sitecore gods and hope they grant us the power to log in from anywhere. Guess I've been doing it wrong all this time.
FR
Freeman
1 year ago
C) Remove all specific host names from the Identity Server configuration settings file and replace them with wild-card options.
DE
Denny
1 year ago
B) Update the role for each user group to include the appropriate site permissions.
JO
Johnetta
1 year ago
A) Patch the web.config for the Content Management instance with the required permission groups.
LE
Leonida
1 year ago
Wait, so we can't just use a magic spell to make Sitecore login work for multiple host names? Darn, I was really hoping for some Harry Potter-style solutions here.
KR
Kristal
1 year ago
C) Remove all specific host names from the Identity Server configuration settings file and replace them with wild-card options.
TI
Titus
1 year ago
B) Update the role for each user group to include the appropriate site permissions.
CH
Cherelle
1 year ago
A) Patch the web.config for the Content Management instance with the required permission groups.
JA
Jacklyn
1 year ago
Option A sounds like a lot of work. Patching the web.config for the Content Management instance with the required permission groups? No, thank you, I'll take the easy route with option D.
KE
Kenny
1 year ago
Yeah, adding AllowedCorsOriginsGroup for each site seems like the way to go.
JA
Jacinta
1 year ago
I agree, I prefer option D for an easier solution.
DO
Dominque
1 year ago
Option A sounds like a lot of work.
IN
Ines
1 year ago
The answer is definitely D. Adding the AllowedCorsOriginsGroup for each site to the Identity Server configuration is the way to go. It's a clean and secure solution.
EN
Enola
2 years ago
I'm not sure about option C. Removing all specific host names and replacing them with wildcards in the Identity Server configuration might not be the best solution, as it could potentially open up security vulnerabilities.
LI
Linwood
1 year ago
I'm not sure about option C. Removing all specific host names and replacing them with wildcards in the Identity Server configuration might not be the best solution, as it could potentially open up security vulnerabilities.
DO
Dorian
1 year ago
C) Remove all specific host names from the Identity Server configuration settings file and replace them with wild-card options.
BE
Benedict
1 year ago
B) Update the role for each user group to include the appropriate site permissions.
FR
Francene
1 year ago
A) Patch the web.config for the Content Management instance with the required permission groups.
CH
Charlene
2 years ago
Option B seems the most straightforward. Updating the role for each user group to include the appropriate site permissions is the logical approach to enable users to log in to the Sitecore shell for multiple host names.
TA
Tashia
1 year ago
Definitely, that way users can log in to the Sitecore shell for multiple host names.
CA
Catalina
1 year ago
It's important to ensure users have the appropriate site permissions.
BU
Buck
1 year ago
I agree, updating the role for each user group makes sense.
TA
Tanja
2 years ago
Option B seems the most straightforward.
FA
Fausto
2 years ago
I think removing all specific host names from the Identity Server configuration settings file and replacing them with wild-card options could also work.
NA
Nadine
2 years ago
I agree with Kenny, updating the role for each user group to include the appropriate site permissions makes sense.
KE
Kenny
2 years ago
I think we should patch the web.config for the Content Management instance with the required permission groups.