Exam SY0-701 topic 1 question 49 discussion

Frankly it should be both A and B. Submitting it to change management does not prevent the issue if it isn't caught by change management, and testing it in non-prod would but also shouldn't be done without a request to change management. It's a different question than the previous one regarding change management: Yes the technician SHOULD put in a change management request first, but that's not the question, the question is what would prevent it and the change management request does not prevent an issue, rather it lets everyone know what is happening and provides a backout plan if issues come up. That still does not PREVENT the issue though so /shrug

Testing the policy in a non-production environment allows for the identification and resolution of any unforeseen issues, such as servers becoming unreachable, before implementing the policy in the production network. This ensures that any potential impact on business operations is minimized.

you got this wrong. change management is not about documenting, it is about evaluating the request. if properly reviewed - it will not be allowed. and we are not talking about who does their work well and not - we cannot speculate if change management fails and this is approved. change manamgement (A) should be correct

B is the best answer. A change request can be submitted and approved, but problems will arise if the approved change is not applied correctly. Testing the change in a non-production environment will reveal errors before they can affect production.

After successful testing and change approval, apply the policy in the production environment.

Maybe i guess

Answer: B Procedurally "A" should and needs to occur first, However those 2 steps by themselves won't prevent this Even though those changes will still have to be tested in a non-production environment. Even if the CAB approves the request, ONLY seeing it in action will let anyone know that it will interfere with servers. Testing is the ACTION that will prevent it.

Testing the policy in a non-production environment allows the technician to identify and fix any unintended consequences before implementing the rule in the production network. This ensures the servers and critical services remain reachable while maintaining security.

. Testing the policy in a non-production environment before enabling the policy in the production network

Test policy in no prod environment

Since the question mentions that the technician has already updates the policy, we can assume that he got approval first to implement the solution. But, for a good technician to perform well and avoid any issues, he should test the changes in a non-production environment. Both questions A and B are good answers, but B est is the best one in this case.

B is something that should have been done. HOWEVER, if we documented the new change and submitted a change request this issue could have been prevented as well.

The answer is "A"! You will get fired if you did not put in a change request before testing or implementing anything! It needs to be documented and approved FIRST! This will determine if you need equipment, resources, special access, or if there's even budget!

The answer is "A"! You will get fired if you did not put in a change request before testing or implementing anything! It needs to be documented and approved FIRST! This will determine if you need equipment, resources, special access, or if there's even budget!

Should be A, check Question #30

Change Management Processes: Schedule maintenance windows, Thorough backout plans, Consistent “testing” post-implementation

A. Documenting the new policy in a change request and submitting the request to change management