1Y0-A19 · Question #3
The design for an environment requires that Web Interface is load balanced across multiple servers. An administrator has been asked to figure one master site and to distribute the configuration of…
The correct answer is B. Set up file sharing permission to allow access over the network to the configuration folder of D. Change the setting of the configuration location parameter of the other sites to point to the. See the full explanation below for the reasoning.
Question
The design for an environment requires that Web Interface is load balanced across multiple servers. An administrator has been asked to figure one master site and to distribute the configuration of that site throughout the Web Interface implementation. Which two steps must the administrator take in order to share the master site's configuration? (Choose two)
Options
- AEdit the bootstrap configuration file of the other sites to point to the IP address of the master
- BSet up file sharing permission to allow access over the network to the configuration folder of
- CReplace the configuration files of the other sites with the master site's configuration file to
- DChange the setting of the configuration location parameter of the other sites to point to the
How the community answered
(40 responses)- A18% (7)
- B70% (28)
- C13% (5)
Community Discussion
9The answer is B and D, and your memory hook is "SHARE the door, STEER the others through it," because B has you open up file sharing permissions so the master config folder is reachable over the network, and D has you change the configuration location parameter on every other site so they all point straight to that shared master folder, drinking from one single source of truth.
Solid mnemonic, though I'd add that on exam day you want to eliminate A and C first by asking what problem each one actually solves, because the stem almost always gives you a clue that rules out local-copy duplication before you even think about which positive steps to pick.
So the other sites are just redirected to read from the master's config share, right, not copying files around?
Right, they read from the share rather than copying, but worth noting that those clients still need a local cache policy set or they'll choke if the share goes offline.
C trips people up because copying the config file sounds logical, but that just gives you a static snapshot with no ongoing sync, so the moment you change something on the master the other sites are already out of date. You need B and D together, share the master's configuration folder over the network and then point each of the other sites at that shared location via the configuration location parameter, that way every site is always reading from one source of truth.
The key here is that "sharing" a master site config means the other sites need to reach it over the network, which points you away from any option that involves copying or replacing files locally. What is your current thinking on why a bootstrap file edit alone would not be sufficient to redirect the config location?
The bootstrap redirect would work for the config path but you still hit the problem that whatever node pulls the config first can cache a stale version locally, so network-shared config only solves half of it unless you also sort out cache invalidation.
A and B, you need the bootstrap pointing to master and file share open so it can actually reach the config.
Hey Carlos, close but the bootstrap pointing to master is actually option A doing double duty with B there, and what you really need alongside B is D for the distribution point access, not A as a separate pick. Think "BD" like "Be Deployed" to lock it in.