Operational Procedures, Backup, and Remote Support Quick Reference for A+ Core 2 220-1202

Operational Procedures is 21% of A+ Core 2. These questions often ask what should happen around the technical work: what gets documented, who approves a change, how recovery is protected, what safety or privacy rule applies, and which support method fits the situation.

1. Operational decision map

2. Write support records another technician can use

Useful support documentation can include:

• User and contact information as permitted
• Device or asset identifier
• Symptoms and business impact
• Time and sequence of events
• Troubleshooting already performed
• Changes made
• Results and current status
• Escalation or ownership
• Resolution and follow-up

A ticket should describe what happened, not merely say "fixed."

Other records serve different purposes:

• Asset management: tracks equipment and ownership/lifecycle details.
• CMDB: records configuration items and relationships in environments that use one.
• Knowledge base: preserves reusable solutions and procedures.
• SLA: defines agreed service targets and responsibilities.
• Onboarding/offboarding records: help ensure accounts, equipment, and access follow employment changes.

Documentation is part of the support work because the next technician may not be the one who performed the fix.

3. Control the path from current state to new state

A practical change-management flow includes:

1. Define the requested change and scope.
2. Assess risk, dependencies, and user/business impact.
3. Obtain required approval.
4. Plan testing, timing, communication, backup, and rollback.
5. Implement the approved change.
6. Validate the result.
7. Document what happened.
8. Review the change afterward when required.

A rollback plan answers how to return to the previous working state if the change fails.

A backup can support rollback, but the two are not identical. Rollback may involve configuration reversal, package downgrade, snapshot restore, or another approved method.

Emergency work may use an accelerated process. It still needs accountability and documentation.

4. Design backups for recovery, not for the feeling of being backed up

Common backup types

• Full: copies all selected data.
• Incremental: copies changes since the most recent backup of any type.
• Differential: copies changes since the last full backup.
• Synthetic full: creates a new full backup from existing backup data without rereading every source file.

The correct restore path depends on the backup method and product.

3-2-1

A common resilience guideline is:

• Keep 3 copies of important data.
• Use 2 different media or storage types.
• Keep 1 copy offsite or otherwise separated from the primary failure domain.

The point is separation from one event, not memorizing the numbers without understanding why.

Test restores

A backup job completing successfully does not prove the required data can be restored.

Useful checks include:

• Restore selected files.
• Validate application-aware backups where required.
• Confirm encryption keys/credentials are available.
• Verify retention matches the requirement.
• Protect backup systems from the same malware or account compromise as production where practical.

If the user asks how quickly service must return or how much data loss is acceptable, those are recovery requirements that should influence backup and restore design.

5. Protect people first, then equipment

Electrostatic discharge

Electrostatic Discharge (ESD) can damage electronic components.

Useful precautions include:

• Use an appropriate antistatic strap/mat when required.
• Handle components by edges rather than contacts.
• Store sensitive components in antistatic packaging.
• Work in an environment that reduces static risk.

Electrical and physical safety

Examples include:

• Remove or isolate power before servicing equipment when appropriate.
• Do not open devices containing dangerous stored electrical energy unless trained and authorized.
• Follow proper lifting technique and use assistance for heavy equipment.
• Keep walkways and cable paths safe.
• Use appropriate fire-extinguisher types and follow site emergency procedures.
• Respect battery damage, swelling, heat, and disposal requirements.

Environmental controls

Temperature, humidity, dust, airflow, surge protection, and Uninterruptible Power Supply (UPS) capability can all affect equipment reliability.

A UPS provides short-term battery-backed power and power conditioning for supported loads. It is not a long-duration replacement for utility power.

6. Treat user data and organizational rules as part of the repair

A technician can have technical access without having permission to inspect unrelated personal or business data.

Relevant concepts include:

• Privacy and regulated information
• Data retention
• Non-Disclosure Agreements (NDAs)
• Acceptable Use Policies (AUPs)
• Software licensing
• Copyright and intellectual-property rules
• Evidence handling and chain of custody when required
• Policy on prohibited content or activity

If suspicious or potentially illegal content is found, follow organizational policy and escalation procedures rather than investigating beyond your role.

Software that technically installs is not necessarily licensed for that user or device.

7. Good support communication reduces technical mistakes

Useful habits include:

• Let the user finish describing the problem.
• Restate the issue when clarification is needed.
• Avoid unnecessary jargon.
• Set realistic expectations for time and impact.
• Explain what will change before disruptive work.
• Protect private information from unnecessary exposure.
• Document commitments and follow-up.
• Escalate when the problem exceeds authority or expertise.

Do not promise an outcome you have not verified. "The change is complete and tested" is different from "This will never happen again."

8. Use scripts for repeatable work, with controls around them

A+ expects recognition of common script types and automation use cases, not advanced programming.

Scripts can help with:

• Repetitive configuration
• File operations
• Inventory or information gathering
• Maintenance tasks
• Simple deployment or support workflows

Risks include:

• Running with excessive privilege
• Hard-coded credentials
• Destructive commands
• Untrusted scripts
• Missing input validation
• Poor error handling
• Running against the wrong systems

Read or validate a script before executing it when the source or effect is uncertain. Automation makes a correct task faster, but it can also make a bad command fail at scale.

9. Choose remote support by interface and trust requirement

SPICE and approved third-party remote-support tools can also appear in the objective scope.

Remote control should be authorized, auditable where required, and limited to the support need. Do not expose management services broadly to the internet simply because remote access is convenient.

10. Use AI as an assistant, not as an authority

The current Core 2 objectives include Artificial Intelligence (AI) basics and appropriate-use concerns.

Important ideas include:

• Follow organizational AI-use policy.
• Do not paste confidential, regulated, credential, or customer data into unapproved AI services.
• Check output for accuracy before using it in a support action.
• Watch for hallucinations, where a system produces confident but false information.
• Consider bias and incomplete context.
• Respect licensing, copyright, plagiarism, and attribution requirements.
• Treat generated commands or scripts like any other unverified code: understand the effect before running them.

AI can help summarize logs, draft documentation, explain an error, or suggest troubleshooting paths. The technician remains responsible for verifying the result and protecting the data used to produce it.

11. Scenario comparisons

A planned software upgrade could interrupt payroll

Use change management: scope, risk, approval, timing, backup/rollback, communication, implementation, validation, and documentation.

Backup dashboard says last night's job succeeded

That is useful evidence, but a restore test provides stronger evidence that required data is recoverable.

Technician finds unrelated private photos while repairing a laptop

Avoid unnecessary access and follow privacy/policy requirements. Technical access does not create a business need to inspect unrelated data.

User needs graphical support on a remote Windows workstation

RDP may fit the interface requirement. Secure the access path and permissions rather than exposing it broadly.

AI-generated command claims it will repair a disk

Read and validate the command before execution. Do not run it against production data merely because the output sounds confident.

A script contains an administrator password in plain text

The automation may work, but the credential handling is unsafe. Protect secrets rather than trading security for convenience.

12. Common exam traps

• Making a managed-system change without approval, rollback, or documentation.
• Treating a successful backup job as proof that restore works.
• Confusing backup with a rollback plan.
• Ignoring ESD because the system is powered off.
• Treating technical access as permission to inspect unrelated user data.
• Using remote-control software when only a secure shell is required.
• Exposing remote-management services directly without considering safer access controls.
• Running an unknown script because it automates the task.
• Assuming AI-generated instructions are correct because they are detailed.
• Uploading sensitive data to an AI tool without checking organizational policy.
• Promising the user a result before validation.
• Investigating suspicious content beyond the technician's authorized role.

13. Rapid review grid

14. Official references

• CompTIA A+ certification page