7 Operational Workflows and Continuous Improvement Online Quiz Questions

True

False

Send every warning to every employee without defining who should respond.

Define the triggering condition, recipient, assessment timeframe, and diagnostic information.

Alert only after an audit confirms that a control has failed.

Use a single threshold for all services so operators can respond consistently.

The service's purpose, owner, and critical dependencies.

Normal operating ranges and conditions that require investigation.

The personal passwords of all service users.

Approved configuration baselines and where authoritative copies are stored.

Recovery priorities, responsible roles, and escalation contacts.

True

False

Restart the application immediately and record no diagnostic information.

Ask users to retry later, since slow access is not a monitoring concern.

Compare application response time, server utilization, network latency, and recent configuration changes, and record the observations together.

Treat the report as proof of an attack and disable all network connections.

The time of the event.

Personal opinions about who is at fault.

Observations and affected services.

Decisions and actions taken.

Unverified conclusions recorded as established facts.

The people responsible for the actions.

Accept the deviation if the system still appears to function.

Overwrite the configuration history so it matches the current state.

Wait until the next scheduled audit before taking any action.

Investigate the cause and reconcile the deviation with approved changes.

Restore the application first, then attempt to restore identity, DNS, network connectivity, and databases as needed.

Check that restoration assets are usable and trustworthy, restore dependencies before the application, and test restored systems before returning them to normal operation.

Restore whichever service is easiest first, then rely on user reports to determine whether the rest are working.

Start the application server and consider recovery complete once it runs.

True

False

Treat every warning as an incident so no alert is overlooked.

Tune alert thresholds and investigate repeated false alarms.

Disable alerts that occur more than once.

Use the same alert threshold for every service.

Only the organization’s internet-facing firewalls and their software versions.

Only wireless systems and the devices connected to them.

Routers, switches, firewalls, wireless systems, network services, and critical connections between them.

Only network devices that have recently generated an alert.

Assign an owner, priority, due date, and closure evidence.

Record the finding’s title and the date of the next audit only.

Assign a priority and close the finding without recording evidence.

Assign a due date and leave ownership and priority undecided.

Skip approval and documentation because the change is urgent.

Wait for the ordinary approval process even if delay prolongs immediate harm.

Implement the change and document it only if it causes a problem.

Use expedited approval, then record the change promptly, review it afterward, and check the resulting configuration.