MENU
To enable LDAP over SSL for a Vault when DNS lookups are blocked, which step must be completed?
Suggested Answer: A
Get Premium PAM-SEN Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
29 comments · newest first
BR
Brianne
10 months ago
Nope, it's definitely A. Trust me on this!
DA
Dawne
10 months ago
Wait, is that really necessary?
DO
Dorthy
10 months ago
Gotta add FQDN & IP to the hosts file!
GA
Galen
10 months ago
Totally agree, that's the way to go.
DO
Dorathy
11 months ago
I think it's option C, just use IPs.
JA
Jaclyn
11 months ago
Setting the ReferralsDNSLookup parameter to 'No' seems like it could help, but I wonder if that's the main step we need to focus on for SSL.
MI
Miss
11 months ago
I practiced a similar question where we had to ensure LDAP hosts were defined correctly. I feel like using only IP addresses might be important here.
AD
Adell
11 months ago
I remember something about configuring DNS settings, but I can't recall if it's about allowing outbound TCP 53 or something else.
NI
Nina
11 months ago
I think we might need to add the FQDN and IP details to the local hosts file, but I'm not entirely sure if that's the only step required.
WI
Willow
12 months ago
This is a good question. I'll need to review my notes on LDAP configuration to make sure I'm approaching it the right way.
RE
Reita
12 months ago
I'm pretty confident I know the answer to this one. It's option A - adding the FQDN and IP details to the local hosts file. That's the way to go when DNS lookups are blocked.
MA
Maile
12 months ago
Okay, I think I've got this. The key is to add the FQDN and IP details for the LDAP hosts into the local hosts file on the Vault server. That should do the trick.
CA
Catina
1 year ago
Hmm, I'm a bit confused by the wording of the question. I'll need to re-read it a few times to make sure I understand what they're asking.
NI
Nicolette
1 year ago
This looks like a tricky one. I'll need to think through the steps carefully to make sure I get the right answer.
NI
Nikita
1 year ago
I'm feeling option A. Editing the hosts file is always a reliable way to bypass DNS issues. It's like going back to the stone age of networking!
YE
Yesenia
1 year ago
I think option B might be more practical in this situation. Allowing outbound TCP 53 could solve the issue.
RE
Reynalda
1 year ago
I agree, editing the hosts file is a classic workaround for DNS problems.
CH
Chau
1 year ago
D all the way! Turning off DNS lookups is the simplest solution. Who needs those pesky domain names anyway?
CH
Chauncey
1 year ago
B) Configure an AllowNonStandardFWAddresses rule in DBParm.ini on the Vault to allow outbound TCP 53 to the organization's DNS servers.
JO
Johanna
1 year ago
A) Add the FQDN & IP details for each LDAP host into the local hosts file of the Vault server.
HO
Holley
1 year ago
A) Add the FQDN & IP details for each LDAP host into the local hosts file of the Vault server.
CA
Carylon
1 year ago
I'm not sure, but I think B) Configure an AllowNonStandardFWAddresses rule in DBParm.ini on the Vault to allow outbound TCP 53 to the organization's DNS servers could also be a valid option.
JA
Jani
1 year ago
Haha, option B is a classic! Trying to open up the firewall for DNS traffic? That's like trying to solve a broken leg with a bandaid.
BE
Bernardine
1 year ago
For LDAP over SSL, I'd go with option C. Using IP addresses is the way to go when DNS lookups are blocked. No need to mess with the hosts file or firewall rules.
CH
Chandra
1 year ago
Yeah, no need to complicate things with the hosts file or firewall rules.
BR
Brinda
1 year ago
I think using IP addresses is the most reliable solution.
CH
Charlena
1 year ago
I agree, option C is the best choice in this situation.
HY
Hyun
1 year ago
I disagree, I believe the correct answer is D) Set the ReferralsDNSLookup parameter value to ''No'' in the directory configuration.
VI
Virgina
1 year ago
I think the answer is A) Add the FQDN & IP details for each LDAP host into the local hosts file of the Vault server.