I don't have actual experience, but I'm pretty sure as long as you can compartmentalize thoughts sufficiently, you'll probably pass the poly easy. Hear the question, don't listen to it, don't break it down, don't analyze it, and keep your mind away from your answer and why you're saying what you're about to say, and just say it. I feel the danger lies with if you start to slip up with the compartmentalizing technique and you accidently "think" on the question and/or answer even for a fraction of a second - my guess is, these are what cause those little needles to register spikes. I tried to make it very clear, I have no actual experience, this is all just a guess.

Think about this for a second..... do you think there are very many people whom, by the age of 30, haven't broken over 100 laws (truthfully its probably absurdly higher) ? On average, a person probably breaks a law, however obscure, many times a day.

Haha, technically... Apple just disqualified every FBI Agent that owns an iphone....

DISQUALIFIED! NEXT?

Yes it is. It leads to horrible, horrible, things like ginseng! http://www.realfarmacy.com/doz...

From a reliable source I can also say that you can fail out from reasonable mistaken discrepancies. You see, tbe length of tbe questionarre is no coincidence. They dont want you to be able to recall what you put down as an answer originally and if you originally said you had moved 4 times in the last 10 years and during the poly you remembered a 5th move, and simply just forgotten originally, and you later say 5.... will easily disqualify you. Their method is flawed and im sure they've disqualified potentially amazing would-be agents over ridiculously stupid technicalities.

Over 50 and straight edged boy scout

Note, this guy *does* note that OP mentions security.

I dont think you should have gotten down modded because you make a valid point about their apparent scoring system and then you give a nice opinion based input that all make good sense.

This is just my personal opinion and im not saying this is the correct answer. This is my answer... Best distro overall of 2014? Arch Linux. The distro's affinity for clean and clear scripts on top of the way you build your system never ceases to teach me new things all the time. Best distro for the new user of 2014? Mint. Clean and simple package management. Best distro for business servers of 2014? CentOS 7. It is very well polished, rock stable, and dead simple Windows Active Directory integration. I lub Linux =B

The selfishness bringing this terrible disease to your county... immoral fucking asshole

While im not saying its okay to dig up personal information through google searches and then freaking out the girl by sharing the information the creep dug up, I do find it concerning that she is victim blaming google for finding this information that she was responsible for making public in the first place. Google doesn't make available information that you hadn't posted online in the first place.

ZFS not liking raid is not a con but more an alernative. ZFS does what raid controllers do but in software. Plenty of advantages not the least of which it does raid faster, uses your ram as a very large cache, does not have the raid 5 write-hole bug. Would you want to run a hardware raid off of another hardware raid controller? ZFS has fantastic performance. It does love memory but it uses it well. Ive been using ZFS on Archlinux for over two years and have had 0 zfs failures. The only expandability issue people run into is when you want to increase your zvol device it has to match the size of the others in the same volume. Btrfs has advantages in this area as its been designed with releveling in mind but zfs generally outperforms everywhere else.

Correct but I think the reason there's so much pushback is because it wont be long before it's not just an alternative with backward compatibility and it becomes the only way. Stepping us in that direction.

What us geeks dislike about it is much the same reason we dislike systemd: its an abstract layer between you and the configuration of your services/daemons. We like init.d in that we can script those daemons and even add on to those init scripts if we choose. Where as windows services puts this wall between you and that sweetness. And systemd is pushing us in that direction and OP's last comment in the summary is ringing more and more true.