As an administrator, I must have a good sense of prioritizing improvements based on their related impacts on service, considering peak demand times and long-term network design. For each change, we need to develop a change plan that includes a rollback plan, outlining the necessary steps and ensuring that all teams and relevant stakeholders are informed about the changes. However, there are often sticky situations where immediate changes are required. I try to minimize these urgent changes by implementing low-cost, necessary adjustments as soon as possible.

1. Check impact on service - check how it impact the service in daily operations 2. Pan for upgrades - plan the upgrade time when traffic is low to minimize disruption 3. Do the health checkup regularly

Prioritizing is important in the case, address immediate disruptions affecting critical services, such as outages or security vulnerabilities. Use quick fixes to minimize downtime while planning a permanent solution and for long term solution: Focus on upgrades if the current infrastructure poses recurring issues, scalability challenges, or technical debt. Examples: Replacing outdated hardware, transitioning to a more scalable architecture, or implementing automation tools.

There should be a guide line base on standards like ITIL, ISMS,.... so no one can do personalize act Doing base on policy is one of the most important part of security and reliability. IT Guide line must Compilation accurately base on standard and best practice and upgrade continuously.

I prioritize quick fixes when they directly impact business operations or user experience, ensuring minimal downtime and immediate continuity. However, I balance this with planning and implementing long-term upgrades that enhance system performance, security, and scalability. Effective communication with stakeholders and understanding the organization's priorities help me make informed decisions on allocating resources to both short-term and long-term needs.