* B (Support availability):Defines hours of service and whether support is available 24/7 or during business hours.
* E (Resolution time):Specifies the timeframe within which the service provider commits to resolve incidents.
Other options explained:
* A: Cost and size are contractual, not SLA performance metrics.
* C: Sustainability is long-term environmental or operational, not SLA-specific.
* D: Reliability is often captured as uptime or availability but not as a discrete SLA support term.

* HIPAA requires integrity controls to prevent unauthorized data modification.
* D (Technical integrity and transmission security): Ensures PHI data is protected against unauthorized alteration during storage and transmission.
* This directly addresses the issue of data being altered without consent.
Why other options are incorrect:
* A: Prevents unauthorized access but does not guarantee data integrity.
* B: Administrative processes cover policies, not technical enforcement.
* C: Focuses on physical device control, not data integrity.
-

When multiple virtualized network zones (such as VRFs, virtual firewalls, or logical partitions) are consolidated onto a single physical device, the primary concern is:
* A (Fate sharing): A single hardware failure, software crash, or resource exhaustion event could simultaneously impact all virtualized zones, creating a shared risk across multiple otherwise isolated services.
Other options explained:
* B: CPU resource allocation can be controlled via resource management but is not the primary risk.
* C: Congestion control is typically a traffic engineering issue, not a virtualization risk.
* D: Security isolation can be maintained through proper virtualization boundaries.
* E: Bandwidth can be managed through QoS and resource allocation.
-

* Performance management is the FCAPS function responsible for collecting statistics, monitoring utilization, identifying performance degradation, and optimizing network responsiveness.
* It ensures that the network maintains SLA targets.
Why other options are incorrect:
* A: Fault management detects and responds to failures.
* B: Accounting tracks resource usage.
* D: Security handles access and policy enforcement.

* SNMPv3 is recommended as it supports authentication and encryption, protecting SNMP traffic even across service provider MPLS VPN backbones.
* Healthcare environments require strong privacy and compliance (e.g., HIPAA), making SNMPv3 the correct protocol.
Why other options are incorrect:
* B & C: Syslog is unrelated to SNMP traps.
* D: SNMPv2 lacks security (unencrypted community strings).
* E: SSH secures CLI access but not SNMP.