To ensure that the Traps VDI tool can obtain verdicts for all unknown files what are the things that needs to be checked? Assuming ESM Console and ESM Server are on different servers. (Choose two.)
I’m a bit confused about the roles here. Does the Endpoint really need to access the ESM Server, or is it more about the WildFire connection? I wish I had reviewed this more.
I feel like this is similar to a practice question we did about server communications. I think the ESM Console's access to the WildFire Server could be important too.
I'm not entirely sure, but I remember something about the Endpoint needing access to the WildFire Server as well. It might be one of the options we need to consider.
I think I've got a good handle on this. The key is to ensure that the ESM Server can access the WildFire Server, and that the Endpoint can access the WildFire Server. Those seem to be the two critical connections that need to be checked to ensure the Traps VDI tool can get the necessary verdicts.
This is a tricky one. I'm not entirely sure what the Traps VDI tool is or how it relates to the ESM Console and ESM Server. I'll have to read through the question carefully and try to break it down step-by-step.
Okay, I've got this. The question is asking about the things that need to be checked to ensure the Traps VDI tool can get verdicts for all unknown files. So I need to focus on the connectivity between the ESM Server and the WildFire Server, as well as the connectivity between the Endpoint and the WildFire Server.
Hmm, I'm a bit unsure about this one. I know we need to ensure the Traps VDI tool can get verdicts, but I'm not sure exactly what that means in terms of the components that need to be checked. I'll have to think this through carefully.
This question seems straightforward. I think the key is to focus on the connectivity between the different components - the ESM Server, ESM Console, and WildFire Server.
Wait, do I need to check if the WildFire server can access the ESM Server? Or is that just a distraction? I better double-check the question and make sure I understand the requirements.
Haha, I bet the person who wrote this question was having a good laugh. 'Endpoint can access ESM Server'? As if we want our endpoints to be able to just waltz right into the server! I'll steer clear of that one.
Ah, I see! The key is that the ESM Server needs to be able to access the WildFire server, since it's the one doing the analysis. And the ESM Console needs to be able to communicate with the WildFire server to get the verdicts. Glad I read the question carefully!
Yes, that's correct! The ESM Server needs to access the WildFire Server for analysis, and the ESM Console needs to communicate with the WildFire Server for verdicts.
I'm not sure about this one. Do we really need the endpoint to access the WildFire server? Isn't the whole point of Traps VDI to protect the endpoint from unknown files?
Hmm, I think the correct answers are A) and C). The Traps VDI tool needs to communicate with the WildFire server to obtain verdicts, and since the ESM Console and ESM Server are on different servers, the ESM Console needs to be able to access the WildFire server directly.
Becky
3 months agoShaunna
3 months agoDarrin
3 months agoGeoffrey
4 months agoTarra
4 months agoGretchen
4 months agoDino
4 months agoAnglea
4 months agoCecil
5 months agoDean
5 months agoIra
5 months agoWalton
5 months agoSusana
5 months agoJoaquin
5 months agoJacqueline
9 months agoLeatha
8 months agoToi
9 months agoBeula
9 months agoEugene
9 months agoCorazon
10 months agoJohana
9 months agoAlison
9 months agoBurma
9 months agoCrista
10 months agoTwila
8 months agoSkye
9 months agoNana
9 months agoEdgar
10 months agoMajor
10 months agoAvery
8 months agoLili
8 months agoDaisy
9 months agoSena
10 months agoErasmo
11 months agoCarlene
11 months agoSueann
11 months ago