An administrator troubleshooting a pilot notices that network controls between the mainframe and the target environment were disabled to get an early demo working faster. What is the risk with this approach?
Select an answer to reveal the explanation.
Short Explanation
You're trading a properly planned, secured connection for an open one, exposing source code and data in transit. And once the demo works, it's easy to forget to turn the controls back on.
Full Explanation
The correct answer is the one stating that disabling network controls trades a properly planned, secured connection for an open one, exposing source code and data in transit until controls are reinstated, which is easy to forget once the demo succeeds. Network controls protect what travels between environments, and turning them off removes that protection for as long as they stay off, often longer than intended. The answer saying there is no risk until general availability is wrong because a pilot still carries real source code and data that need protecting. The answer saying it only affects demo performance is wrong because disabled controls affect confidentiality and integrity, not just speed. The answer saying disabling controls is required for any pilot is wrong because pilots run successfully with controls in place when connectivity was properly planned. For the exam, flag disabled network controls as a finding requiring remediation, not a normal pilot cost.