Network Strategy, Governance, Resilience and Sustainable Transformation

Introduction

Advanced communication networks are no longer planned only as collections of routers, radio systems, optical links and servers. They are strategic infrastructures that support commerce, public administration, health care, education, emergency response and industrial automation. Their design therefore involves technical performance, financial viability, regulatory legitimacy, social inclusion, environmental responsibility and organizational capability.

Network transformation is the deliberate movement from a current operating model to a desired future state. It may involve 5G and 6G evolution, cloud-native cores, software-defined networking, edge computing, automation, artificial intelligence (AI), disaggregated hardware, open interfaces and improved cybersecurity. Transformation is successful only when these technologies create measurable value while controlling risk and preserving public trust.

This chapter develops an integrated approach to network strategy, governance, resilience and sustainable transformation. It combines capacity planning, techno-economic analysis, sourcing, standards, regulation, risk assessment and performance management. It also examines disaster recovery, net neutrality, digital inclusion, ethical AI, energy efficiency and responsible e-waste management.

Learning Objectives

After completing this chapter, a student should be able to:

1. formulate a network transformation roadmap aligned with institutional and societal objectives;

2. apply capacity-planning and techno-economic methods to investment decisions;

3. construct governance, sourcing, standards and regulatory controls;

4. assess network risks and design resilience and disaster-recovery capabilities;

5. evaluate net neutrality, digital inclusion and ethical AI issues;

6. identify energy and e-waste interventions using life-cycle thinking; and

7. define meaningful KPIs and make evidence-based strategic recommendations.

1. Network Strategy as a Socio-Technical Discipline

A network strategy specifies how infrastructure, services, people, suppliers and governance will evolve to meet future demand. It should connect four levels:

• Purpose: the outcomes the network must enable, such as reliable remote learning or low-latency industrial control.
• Capabilities: required properties, including coverage, throughput, availability, security, programmability and observability.
• Architecture: physical, logical and operational arrangements that provide those capabilities.
• Execution: investments, sourcing, skills, migration, controls and performance measurement.

A useful strategy distinguishes outcomes from outputs. Installing 1,000 access points is an output; increasing rural broadband adoption or reducing service interruption is an outcome. Strategic plans that measure only equipment deployment can report apparent success while failing users.

A transformation portfolio normally contains three horizons. The first stabilizes the existing network through lifecycle replacement, configuration control and security remediation. The second modernizes platforms through virtualization, automation, cloud integration and open interfaces. The third explores new services such as network exposure APIs, private networks, edge applications and intelligent operations. Each horizon requires different investment criteria and risk tolerance.

Important terminology

Network transformation is coordinated technical and organizational change in network capabilities and operations. Technical debt is the future cost created by expedient design choices, obsolete platforms or undocumented dependencies. Vendor lock-in is the loss of practical freedom to change supplier because of proprietary interfaces, skills, data or migration costs. Total cost of ownership (TCO) includes acquisition, deployment, operation, support, energy, compliance, migration and disposal costs. Service-level agreement (SLA) is a contractual commitment concerning measurable service attributes and remedies.

2. From Strategic Intent to a Transformation Roadmap

A defensible roadmap begins with a baseline. The baseline should document topology, traffic, assets, software versions, contracts, skills, energy use, incidents, regulatory obligations and end-of-life exposure. Interviews and service data should supplement automated discovery because undocumented dependencies are common.

The target state is expressed through capabilities rather than brand names. For example, “policy-controlled, observable multi-domain service orchestration” is more durable than “deploy product X.” Architecture principles may include security by design, least privilege, open standards where feasible, automation before scale, reversible decisions and separation of control from data ownership.

A roadmap then sequences initiatives according to value, dependency and risk. Typical gates are:

1. Discover: establish baseline, stakeholder needs and constraints.

2. Assess: identify gaps, options, risks, TCO and benefits.

3. Design: define target architecture, controls, migration and acceptance criteria.

4. Pilot: test in a bounded environment with rollback capability.

5. Scale: industrialize engineering, operations, training and supplier management.

6. Optimize: use KPI evidence to refine capacity, cost, energy and service quality.

A portfolio board should approve not only projects but also explicit non-investment decisions. Delaying a project can be rational if uncertainty is high, standards are immature or a lower-cost alternative is emerging. Real-options reasoning treats pilot expenditure as the price of learning and preserving future choices.

3. Capacity Planning and Service Engineering

Capacity planning translates demand forecasts into infrastructure, spectrum, transport, processing and operational requirements. Demand should be segmented by application, geography, time, user class and quality requirement. Average traffic alone is insufficient: busy-hour concentration, mobility, burstiness and redundancy determine engineering capacity.

For a simple traffic estimate, if there are \(N\) active users, each generating average busy-hour traffic \(r\) bit/s, and an engineering headroom factor \(h\), required aggregate capacity is

\[

C_{req}=N r(1+h).

\]

Here, \(h\) is dimensionless; for 25% headroom, \(h=0.25\). This expression assumes the average rate is already measured for the relevant busy period and that statistical multiplexing is not modeled explicitly. It is not a substitute for radio link budgeting, queueing analysis or application-specific latency analysis.

For resilient infrastructure, capacity must also be evaluated after a failure. If total installed capacity is \(C_{tot}\), capacity lost in the worst credible failure is \(C_{fail}\), and required service capacity is \(C_{req}\), a basic survivability condition is

\[

C_{tot}-C_{fail} \geq C_{req}.

\]

This condition addresses capacity, not geographic diversity, restoration time or control-plane dependencies. A network can satisfy it and still fail if both paths share a duct, power system or software controller.

Worked example: capacity and investment timing

An enterprise has 18,000 active users. Busy-hour demand is estimated at 1.2 Mbit/s per user. Planning headroom is 30%. Thus,

\[

C_{req}=18{,}000\times1.2\times1.30=28{,}080\text{ Mbit/s}=28.08\text{ Gbit/s}.

\]

If the largest credible link failure removes 8 Gbit/s, installed capacity must be at least 36.08 Gbit/s to maintain the requirement after failure. A design offering 40 Gbit/s has 3.92 Gbit/s of post-failure margin. The conclusion is conditional: the forecast, headroom, failure model and traffic distribution must be validated before procurement.

Forecasting should use scenarios rather than a single deterministic curve. A baseline, high-growth and constrained-adoption scenario can be combined with sensitivity analysis for user growth, video intensity, cloud adoption and regulatory changes. Capacity triggers should be stated in advance, such as sustained busy-hour utilization above 70% for three months or forecast reserve below a defined threshold.

4. Techno-Economic Analysis

Techno-economic analysis compares alternatives using both engineering outcomes and financial consequences. Relevant cost categories include capital expenditure (CAPEX), operating expenditure (OPEX), spectrum or site costs, energy, software subscriptions, labor, training, cybersecurity, compliance, migration, outages and decommissioning.

The net present value (NPV) of a project is

\[

NPV=-I_0+\sum_{t=1}^{T}\frac{B_t-C_t}{(1+d)^t}+\frac{S_T}{(1+d)^T},

\]

where \(I_0\) is initial investment, \(B_t\) and \(C_t\) are benefits and costs in year \(t\), \(d\) is the discount rate, \(T\) is the analysis period and \(S_T\) is terminal or residual value. All monetary values must use the same price basis and currency convention. NPV is meaningful only when cash flows, discounting assumptions, tax treatment and risk are defined consistently.

The equivalent annual cost (EAC) can compare alternatives with different lives. For a present cost \(P\), discount rate \(d\), and life \(n\), the capital-recovery factor is

\[

CRF=\frac{d(1+d)^n}{(1+d)^n-1},\qquad EAC=P\,CRF.

\]

This calculation assumes a constant discount rate and regular annual periods. It should be combined with annual operating costs and expected residual value rather than used in isolation.

Benefits may include avoided leased capacity, reduced energy, lower incident loss, faster service creation, improved customer retention and compliance avoidance. Some benefits are difficult to monetize. A multi-criteria decision analysis can score cost, resilience, security, interoperability, sustainability and strategic flexibility, but weights must be disclosed because they express organizational values rather than objective facts.

Illustrative economic comparison

Suppose a five-year modernization has an initial cost of $4.0 million, annual net benefit of $1.3 million, no terminal value, and a discount rate of 8%. The present value of the five annual benefits is approximately $5.19 million, giving an NPV of approximately $1.19 million. This supports investment under the stated assumptions. However, a sensitivity test should vary benefit realization, energy prices, migration delay and discount rate. A positive NPV is not a guarantee of success; it may conceal unacceptable concentration risk or social exclusion.

5. Governance, Sourcing, Standards and Regulation

Network governance assigns decision rights, accountability and escalation paths. It is distinct from management: management executes approved work, whereas governance determines who may approve architecture exceptions, risk acceptance, data use, supplier changes and service priorities.

A practical governance model includes:

• a strategy board that sets outcomes, funding and risk appetite;
• an architecture authority that controls principles, interfaces and technical debt;
• a security and privacy function that performs assurance and incident oversight;
• a service council that represents users and operational priorities; and
• independent audit or regulatory assurance where required.

RACI matrices clarify who is responsible, accountable, consulted and informed. Decision records should state alternatives considered, assumptions, evidence, owner, review date and reversal conditions.

Sourcing and supplier strategy

Sourcing choices include single-vendor procurement, multi-vendor integration, managed service, open-source components, strategic partnership and internal development. No option is universally superior. Multi-vendor designs can reduce dependency but increase integration, testing and accountability costs. Open source can improve transparency and innovation, but does not eliminate support, security, licensing or skills costs.

Contracts should address interoperability, data portability, security updates, vulnerability disclosure, audit rights, service credits, subcontractors, exit assistance, spares, software escrow where appropriate, carbon reporting and secure asset disposal. Acceptance testing must assess real service behavior rather than only equipment conformance.

Standards and regulation

Standards promote interoperability, safety and predictable interfaces; regulation establishes legally enforceable obligations. Standards may be international, national, sectoral or de facto. Conformance to a standard does not automatically establish security or fitness for a particular use. Architecture teams should maintain a standards register showing applicability, version, mandatory status, implementation evidence and sunset risk.

Regulatory analysis should consider spectrum licensing, competition, lawful access, privacy and data protection, cybersecurity reporting, accessibility, critical-infrastructure obligations, consumer protection, net neutrality, environmental rules and cross-border data transfer. Legal requirements vary by jurisdiction, so professional decisions require current legal review rather than assumptions based on another country.

6. Risk, Resilience and Disaster Recovery

Risk is commonly analyzed as a combination of likelihood and consequence, but a simple product can mislead when data quality is poor or consequences are multidimensional. A mature assessment identifies assets, threats, vulnerabilities, existing controls, scenarios, impacts, dependencies and treatment options. Impacts should include safety, confidentiality, integrity, availability, finances, rights, reputation and societal effects.

Resilience is the capability to prepare for, absorb, recover from and adapt to adverse events. It is broader than reliability. Reliability concerns failure-free operation under specified conditions; resilience includes adaptation to conditions outside the original design envelope.

Key continuity measures include:

• physical and logical path diversity;
• redundant power, cooling, identity and management systems;
• geographic separation of critical sites;
• tested backups and independent recovery credentials;
• failover automation with human override;
• spare equipment and alternative suppliers;
• incident command and communication procedures; and
• regular exercises involving suppliers and public agencies.

Recovery point objective (RPO) is the maximum tolerable amount of data loss measured in time. Recovery time objective (RTO) is the target time to restore a service after disruption. They are service requirements, not merely infrastructure properties. A zero-minute RPO may be technically possible for some systems but economically or operationally unjustified.

Disaster recovery should identify dependencies. Restoring a virtual machine does not restore a service if DNS, identity, key management, orchestration, licensing or external connectivity is unavailable. Recovery tests should record achieved RTO/RPO, data integrity, operator workload, deviations and corrective actions. “Backup completed” is not evidence of recoverability.

7. Public Interest, Regulation and Ethical AI

Net neutrality

Net neutrality debates concern whether network operators may discriminate among lawful content, applications, users or services. Policy regimes differ, but common analytical questions are whether traffic management is transparent, necessary, proportionate, application-agnostic and subject to oversight. Legitimate congestion management, emergency traffic and specialized services may require differentiated treatment, yet such mechanisms can become covert commercial discrimination. Network strategies should document classification rules, performance effects, disclosure, complaint handling and monitoring.

Digital inclusion

Digital inclusion is not achieved by coverage alone. It includes affordability, suitable devices, accessibility, relevant skills, language support, trust, safe use and meaningful content. A transformation roadmap should therefore track adoption and quality across income, geography, gender, age, disability and other relevant groups, while protecting privacy and avoiding stigmatizing data practices. Subsidized access, community networks, public access facilities, device refurbishment and accessible design can complement infrastructure investment.

Ethical AI in network operations

AI may forecast traffic, detect anomalies, optimize energy, predict failures and assist configuration. Risks include biased training data, false positives, opaque decisions, automation cascades, surveillance, insecure models and unclear accountability. Responsible deployment requires:

1. a defined purpose and necessity assessment;

2. data provenance, quality and minimization;

3. evaluation against safety and subgroup performance criteria;

4. human oversight proportional to consequence;

5. logging, explainability appropriate to the decision and appeal mechanisms;

6. security testing against poisoning, evasion and prompt or model abuse; and

7. continuous monitoring, rollback and retirement criteria.

An AI system that recommends a low-risk maintenance window may require less oversight than one that automatically disconnects a hospital or deprioritizes a community. Governance must be risk-based, with accountable owners even when a supplier provides the model.

8. Sustainable Network Transformation

Sustainability involves environmental, social and economic dimensions across the life cycle. Energy efficiency should be evaluated per useful service, not only per device. Useful indicators may include kWh per transported terabyte, energy per active subscriber, renewable-energy fraction, equipment utilization and embodied carbon per delivered capacity. The denominator must be defined consistently; otherwise apparent improvements may reflect changing traffic mix.

Energy interventions include efficient radios and processors, sleep modes, dynamic cooling, virtualization with workload consolidation, renewable procurement, improved power conversion and reduction of unnecessary traffic. Energy-saving controls must be tested for latency, coverage, availability and recovery impacts. Turning off capacity without understanding demand can reduce resilience or harm rural users.

Life-cycle assessment considers raw materials, manufacturing, transport, deployment, operation, repair, reuse, recycling and disposal. Responsible e-waste management prioritizes life extension through repair and software support, redeployment, certified refurbishment and material recovery. Data-bearing equipment requires verified sanitization or destruction. Suppliers should disclose downstream processors and provide chain-of-custody evidence. Exporting obsolete equipment to jurisdictions lacking safe treatment is not a sustainable solution.

Sustainability KPIs should be paired with service and equity KPIs. For example, reducing energy per bit while increasing outage duration is not an unqualified improvement. Balanced scorecards prevent optimization of one dimension at the expense of another.

9. Performance Measurement and Continuous Improvement

KPIs should be tied to decisions. A useful KPI has a precise definition, data owner, collection method, target, tolerance, reporting period and corrective action. Examples include:

• availability and outage minutes by critical service;
• 95th or 99th percentile latency, not only average latency;
• packet loss and throughput under busy-hour conditions;
• time to detect, respond, contain and recover from incidents;
• change-failure rate and automation coverage;
• capacity reserve after credible failure;
• cost per site, user or delivered unit of traffic;
• energy per useful service unit;
• percentage of assets with supported software;
• recovery-test success rate;
• supplier concentration and exit readiness; and
• adoption and quality gaps among underserved groups.

KPI design must resist gaming. If teams are rewarded only for rapid change, they may increase outages; if rewarded only for availability, they may avoid necessary modernization. Leading indicators, such as unsupported assets and overdue patches, should accompany lagging indicators, such as incidents. Statistical baselines and control limits are useful when sufficient historical data exists, but managers should not mistake correlation for causation.

10. Integrated Illustrative Case: Regional Learning Network

This is a fictional illustrative case. A regional education authority operates a heterogeneous network connecting 120 schools, two data centers and remote learning users. Demand has grown rapidly, the core is approaching vendor end of support, rural schools experience unstable backhaul, and energy costs have increased. A proposed transformation includes cloud-managed access, a virtualized core, AI-assisted capacity forecasting and a new managed-services contract.

Background and problem

The authority has incomplete asset records, a single major supplier for core equipment, backups that have never undergone a full recovery test and no consistent accessibility or adoption data. The procurement team favors the lowest five-year bid, while school leaders prioritize reliability during examinations. Civil-society organizations request affordable access for low-income families.

Analysis

The strategy team first establishes outcomes: examination-period availability, equitable access, secure student data, manageable operating cost and lower energy intensity. It discovers that a nominally redundant data-center design shares a metropolitan power corridor. Capacity analysis shows that the busy-hour requirement is 28.08 Gbit/s; after the largest modeled link failure, at least 36.08 Gbit/s of installed capacity is required. A 40 Gbit/s design meets the arithmetic condition, but a separate geographic path is still required.

The economic model includes equipment, licenses, migration labor, training, energy, managed-service fees, outage exposure and disposal. A multi-criteria assessment gives explicit weights to resilience, inclusion and sustainability rather than allowing price to dominate implicitly. The authority also identifies exit requirements because the proposed cloud platform uses proprietary telemetry and automation interfaces.

Approach and solution

The roadmap uses three phases. First, it inventories assets, upgrades unsupported security components, creates immutable backups and performs a recovery exercise. Second, it pilots the virtualized core and AI forecasting in ten schools, with human approval for all configuration changes. Third, it scales only after meeting service, security, accessibility and energy acceptance tests.

The contract requires open data export, documented APIs, vulnerability notification, subcontractor disclosure, secure erasure and transition assistance. Rural schools receive priority path diversity and a community-access program combines subsidized service with refurbished devices. Traffic-management policies are published, and any differentiated treatment is reviewed for necessity and neutrality.

Outcome

After the pilot, forecast accuracy improves capacity scheduling, but the AI produces more false alarms for schools with sparse historical data. The authority therefore uses confidence thresholds and human review rather than automatic remediation. Recovery testing reveals that an identity service, omitted from the original plan, prevents complete restoration; it is added to the critical dependency register. Energy intensity falls after workload consolidation, while service availability remains within target.

Learning points

The case demonstrates that transformation is not a procurement event. Baseline quality, dependency analysis, pilot evidence, contractual portability, public-interest safeguards and recovery testing are equally strategic. It also illustrates why a technically attractive solution may require modification when inclusion, explainability or resilience evidence is weak.

Challenges and Limitations

Strategic planning is constrained by uncertain forecasts, incomplete asset data, changing regulation, supplier opacity, skills shortages and competing stakeholder priorities. Financial models can undervalue resilience and public benefits because avoided losses are uncertain. KPI systems can create perverse incentives, and standards may lag emerging architectures. AI can amplify historical operational bias. Sustainability claims may omit embodied emissions or outsourced energy. Finally, resilience investments often appear wasteful until a failure occurs.

These limitations do not justify inaction. They require explicit assumptions, scenario analysis, independent assurance, staged investment, transparent trade-offs and periodic revision. A roadmap should be treated as a controlled hypothesis: evidence from pilots and operations must be allowed to change it.

Best-Practice Checklist

1. Begin with service and societal outcomes, not products.

2. Maintain a verified baseline and dependency map.

3. Model busy-hour demand and credible failures.

4. Compare alternatives using life-cycle cost and sensitivity analysis.

5. Make governance rights, exceptions and accountability explicit.

6. Require interoperability, security, portability and exit provisions.

7. Test disaster recovery rather than merely purchasing redundancy.

8. Apply neutrality, inclusion and accessibility assessments.

9. Use AI proportionately, with human accountability and rollback.

10. Measure energy, embodied impacts and e-waste across the life cycle.

11. Pair efficiency indicators with availability, equity and security indicators.

12. Review the roadmap as evidence, regulation and technology change.

Chapter Summary

Network transformation is a socio-technical strategy linking outcomes, capabilities, architecture and execution. Effective roadmaps begin with a reliable baseline, define a target state, sequence pilots and scale decisions, and use explicit gates. Capacity planning must account for busy-hour demand, headroom and post-failure requirements. Techno-economic analysis combines CAPEX, OPEX, risk, benefits and residual value through tools such as NPV and equivalent annual cost, while recognizing uncertainty and non-financial objectives.

Governance establishes decision rights and accountability; sourcing must address interoperability, security, supplier concentration and exit. Resilience requires diverse dependencies, tested recovery and clear RPO and RTO requirements. Network strategy also has public-interest obligations involving net neutrality, digital inclusion and ethical AI. Sustainable transformation considers energy per useful service, life-cycle impacts, repair, reuse and responsible e-waste handling. Finally, balanced KPIs connect performance measurement to continuous improvement without encouraging narrow optimization.

Key Terms

Network transformation: Coordinated technical and organizational change in network capabilities and operations.

Techno-economic analysis: Evaluation combining engineering performance, costs, benefits, risks and strategic value.

Total cost of ownership: All significant life-cycle acquisition, operating, support, migration and disposal costs.

Capacity planning: Forecasting demand and providing sufficient resources under normal and failure conditions.

Headroom: Reserved capacity above forecast demand for uncertainty and growth.

Resilience: Ability to prepare for, absorb, recover from and adapt to disruption.

Recovery time objective: Target time for restoring a service after disruption.

Recovery point objective: Maximum tolerable data-loss interval.

Governance: Allocation of authority, accountability, oversight and decision rights.

Vendor lock-in: Dependence that makes changing supplier difficult or costly.

Interoperability: Ability of systems from different sources to exchange and use information.

Service-level agreement: Contractual commitment for measurable service performance.

Net neutrality: Principle concerning non-discriminatory treatment of lawful network traffic.

Digital inclusion: Equitable access, affordability, capability, accessibility and meaningful use of digital services.

Ethical AI: Design and operation of AI consistent with fairness, accountability, transparency, safety and human rights.

Life-cycle assessment: Evaluation of environmental impacts across a product or service life cycle.

E-waste: Discarded electrical and electronic equipment and associated components.

Key performance indicator: Defined measure used to monitor performance and guide decisions.

Technical debt: Future cost caused by expedient, obsolete or poorly maintained technical choices.

Review Questions

Short Answer Questions

1. Distinguish a network outcome from a network output.

2. Define RTO and RPO.

3. Why is vendor lock-in a strategic concern?

4. State two dimensions of digital inclusion beyond network coverage.

5. What is the purpose of a KPI owner and corrective-action rule?

Long Answer Questions

1. Explain how a network transformation roadmap can progress from baseline discovery to optimization.

2. Discuss the assumptions and limitations of NPV in network investment decisions.

3. Compare reliability and resilience, giving network examples.

4. Explain governance and sourcing controls needed in a multi-vendor network.

5. Discuss how ethical AI principles should be applied to automated network operations.

Analytical / Application Questions

1. A network has 25,000 users, busy-hour demand of 0.8 Mbit/s per user and 20% headroom. Calculate required aggregate capacity. If the largest failure removes 7 Gbit/s, determine minimum installed capacity for service continuity.

2. Design a KPI framework for a rural broadband transformation that balances availability, affordability, inclusion, energy and security. Explain how each KPI could influence decisions.

3. Evaluate whether a single low-cost managed-service supplier should be selected over a more expensive multi-vendor design. Identify the financial, technical, resilience, regulatory and exit evidence required before deciding.

Multiple Choice Questions with Answers

Question 1

In the capacity model C_req = N r (1+h), what does h represent?

A. Number of active users

B. Planning headroom factor

C. Failure capacity

D. Discount rate

Correct Answer: B. Planning headroom factor

Question 2

Which condition represents capacity continuity after a modeled failure?

A. C_tot + C_fail < C_req

B. C_tot - C_fail ≥ C_req

C. C_fail - C_tot ≥ C_req

D. C_tot / C_fail = C_req

Correct Answer: B. C_tot - C_fail ≥ C_req

Question 3

What does an RPO specify?

A. Target time to restore service

B. Maximum tolerable data-loss interval

C. Maximum link utilization

D. Supplier replacement period

Correct Answer: B. Maximum tolerable data-loss interval

Question 4

Which item is primarily a governance function?

A. Configuring a switch port

B. Allocating decision rights and accountability

C. Measuring optical power

D. Replacing a failed fan

Correct Answer: B. Allocating decision rights and accountability

Question 5

Why should recovery exercises include identity and key-management services?

A. They determine antenna gain

B. They may be critical dependencies for restored services

C. They eliminate the need for backups

D. They reduce spectrum licensing costs

Correct Answer: B. They may be critical dependencies for restored services

Question 6

Which is an example of a digital-inclusion measure?

A. Increasing proprietary lock-in

B. Providing affordable access and accessible devices

C. Removing language support

D. Measuring only backbone throughput

Correct Answer: B. Providing affordable access and accessible devices

Question 7

A key ethical safeguard for high-consequence AI network actions is:

A. Removing all human oversight

B. Using undocumented training data

C. Human accountability, logging and rollback

D. Optimizing only average latency

Correct Answer: C. Human accountability, logging and rollback

Question 8

What does life-cycle sustainability analysis include?

A. Only electricity used during operation

B. Only purchase price

C. Manufacturing, operation, repair, reuse and disposal

D. Only recycling revenue

Correct Answer: C. Manufacturing, operation, repair, reuse and disposal

Question 9

For 18,000 users at 1.2 Mbit/s each and 30% headroom, required capacity is:

A. 18.72 Gbit/s

B. 21.60 Gbit/s

C. 28.08 Gbit/s

D. 30.60 Gbit/s

Correct Answer: C. 28.08 Gbit/s

Question 10

Which contract provision most directly supports exit readiness?

A. Prohibition on data export

B. Open data export and transition assistance

C. Unlimited unilateral price changes

D. No vulnerability disclosure requirement

Correct Answer: B. Open data export and transition assistance