Telecom Assessment

Q: When a scenario mentions “uplink” and “downlink,” what should I confirm before doing any math?

Confirm the duplexing method and the resource split. In FDD , uplink and downlink are separated by frequency (paired spectrum), so questions often hinge on the correct band pairing and duplex spacing. In TDD , uplink and downlink share the same frequency and are separated by time, so the frame pattern, guard periods, and synchronization/interference between neighboring cells become central to the correct answer.

Q: How do I avoid blowing a link budget question with dB/dBm mistakes?

Keep everything in dB units until the very end. Treat dBm as an absolute power level and dB as a gain/loss you add or subtract. If the prompt combines transmitter power, antenna gains, feeder losses, and path loss, compute received power as an algebraic sum in dB. Convert to mW only if the question explicitly asks for linear power.

10 – 63 Questions 12 min

This Telecom Assessment targets the decision points telecom engineers and technicians face on real networks: interpreting RF behavior, choosing appropriate modulation and duplexing, and mapping symptoms to the correct protocol layer. Expect scenarios involving link budgets, QoS tradeoffs, signaling flows, and architecture boundaries (RAN/transport/core) where one missed assumption changes the correct answer.

Start

Choose quiz length

1VHF spans roughly 30–300 MHz.

True / False

2Ethernet switches forward frames based on MAC addresses.

True / False

3In an FDD system, uplink and downlink are separated primarily by:

4A 2.4 GHz Wi‑Fi signal falls into which broad frequency range?

5IP addressing and routing are primarily associated with which OSI layer?

6Higher-order QAM generally needs a higher SNR than QPSK to achieve the same bit error rate.

True / False

7What power level equals 0 dBm?

8Select all that apply. Which functions are typically considered Layer 2 (Data Link) responsibilities?

Select all that apply

9In a TDD radio, what mechanism prevents uplink and downlink transmissions from overlapping while switching direction on the same frequency?

10You are estimating received power for an RF link. Tx power = 18 dBm, Tx antenna gain = 12 dBi, Rx antenna gain = 10 dBi, path loss = 110 dB, and total cable/connector losses = 5 dB. What is the received power (approx.)?

11When combining gains and losses in a link budget, you should add transmit power in dBm directly to receiver sensitivity in dBm.

True / False

12Select all that apply. If you change a link from QPSK to 64‑QAM on the same channel bandwidth, what typically happens?

Select all that apply

13Arrange a sensible troubleshooting order for intermittent packet loss on an Ethernet backhaul link (from first to last).

Put in order

1Check physical layer (cables/optics, light levels, link flaps)

2Review QoS/policing/shaping policies for unintended drops

3Check interface counters (CRC, errors, drops)

4Check congestion/queue drops on the path

5Check routing/ECMP changes and upstream path stability

14Arrange the steps for a basic RF link-budget check (from first to last).

Put in order

1Account for Rx-side gains/losses (antenna gain, feeder loss)

2Subtract propagation losses (path loss, clutter, fading allowances)

3Account for Tx-side gains/losses (antenna gain, feeder loss)

4List transmitter power (dBm)

5Compare received power to receiver sensitivity to determine margin

15Which multiple-access/waveform family is used for the LTE downlink?

16A user reports choppy VoIP audio, and monitoring shows average one-way latency is acceptable but jitter is high. Which feature most directly smooths variable packet arrival times at the receiver?

17A point-to-point radio has Tx power 30 dBm, Tx gain 15 dBi, Rx gain 15 dBi, path loss 120 dB, and total cable losses 4 dB. What received power do you expect (approx.)?

18A SIP phone sends an INVITE, but the proxy replies with “408 Request Timeout” after waiting, and packet capture shows no SIP response from the next hop. Which root cause is most consistent with this symptom?

19Select all that apply. In a simplified RF link budget, which items are typically treated as loss terms (subtracted in dB)?

Select all that apply

20Arrange these actions in a typical microwave backhaul link commissioning workflow (from first to last).

Put in order

1Physically align antennas for maximum RSL

2Run end-to-end throughput/BER tests and document results

3Measure RSL/SNR against design targets

4Verify polarization and feeder losses

5Verify line-of-sight and Fresnel clearance

6Enable/verify adaptive modulation and QoS profiles

21In VoIP networks, what is SIP primarily used for?

22Using the FSPL relationship, increasing frequency by 10× (same distance) increases free-space path loss by approximately how much?

23Select all that apply. Which are propagation-related losses/impairments (not equipment/feedline losses) that can reduce received signal in real deployments?

Select all that apply

Frequent Telecom Assessment Misreads That Flip the Correct Answer

Telecom questions reward careful scoping: many wrong answers come from solving the right problem with the wrong assumptions. These are the most common failure patterns and how to avoid them.

Mixing band labels, channels, and services

Avoidance: Identify whether the prompt is talking about an allocation (licensed band), a channelization plan (e.g., Wi‑Fi channels), or a technology band number (LTE/NR band). Then reason from frequency to propagation and antenna behavior.

Ignoring duplexing and frame structure

Typical miss: Treating TDD like FDD (or vice versa) when interpreting uplink/downlink capacity, guard periods, and interference patterns.
Avoidance: Decide FDD vs TDD first, then interpret uplink/downlink separation (frequency vs time) before selecting an answer.

Getting dB arithmetic wrong in link budgets

Typical miss: Adding mW values directly, or treating dBm (absolute power) like dB (a ratio).
Avoidance: Stay in dB/dBm for gains and losses (algebraic sums). Convert to linear only when explicitly required.

Solving at the wrong layer

Typical miss: Diagnosing an L3 routing problem when the symptom is L2 (VLAN tagging, MTU, duplex mismatch) or L1 (SFP, fiber polarity, RF front-end).
Avoidance: Map each clue to OSI: signaling messages and timers (higher layers) behave differently than physical impairment (noise, fading, attenuation).

Over-trusting “ideal” propagation and traffic

Typical miss: Assuming free-space, no fading margin, or perfectly smooth traffic when the scenario describes indoor penetration, clutter, or bursty congestion.
Avoidance: Look for words like urban canyon, foliage, handover edge, peak hour, and add margin/queueing effects accordingly.

Telecom Engineer Quick Reference: RF, dB Math, QoS, and Layer Mapping

Printable note: You can print or save this page as a PDF to keep this reference sheet for quick review before or after the assessment.

RF + spectrum anchors

VHF: 30–300 MHz (wide coverage, larger antennas).
UHF: 300–3000 MHz (cellular, 2.4 GHz ISM; balance of coverage and capacity).
Microwave: 3–30 GHz (backhaul, 5 GHz Wi‑Fi, some 5G; higher path loss, more LOS sensitivity).

dB and power conversions (get the sign right)

dBm: absolute power referenced to 1 mW.
dB: ratio (gain/loss). Add/subtract in budgets.
Rule of 10: +10 dB = 10× power, +3 dB ≈ 2× power.
dBm to mW: P(mW) = 10^(P(dBm)/10).

Path loss + link budget skeleton

FSPL (dB): 32.44 + 20·log10(dkm) + 20·log10(fMHz).
Received power (dBm): Tx power + Tx antenna gain + Rx antenna gain − (path loss + feeder losses + other losses) − margin.
EIRP concept: “What the transmitter looks like” if it were isotropic: Tx power plus antenna gain minus feeder loss.

Modulation/OFDM intuition (what the question is really asking)

Higher-order QAM: higher throughput potential but requires better SNR/SINR.
More robust schemes: trade spectral efficiency for resilience to noise/fading.
OFDM systems: watch for subcarriers, cyclic prefix, and sensitivity to synchronization and phase noise.

QoS and performance triage

Latency vs jitter: latency is delay; jitter is variation in delay (often worse for voice/video).
Loss: drives retransmissions (TCP) or quality drops (real-time media).
Common markings: DSCP (IP layer), 802.1p/PCP (Ethernet VLAN tag). Ensure marking survives across hops and is mapped to the correct queue.

OSI “fast map” for telecom scenarios

L1: RF, optics, cabling, modulation/line coding, SFP power levels.
L2: VLANs, MAC, LAG, MPLS labels (often treated as “2.5”), MTU/fragmentation symptoms.
L3: IP addressing, routing (OSPF/BGP), TTL/hops.
L4–L7: TCP/UDP behavior, SIP/IMS call flows, application timers and retries.

Telecom Job Task Map: What This Assessment Mirrors on Real Networks

This assessment aligns to day-to-day tasks across RAN, transport, core, and customer-facing operations. Use the map below to connect question themes to the work outputs that hiring managers and lead techs care about.

RF engineering and field optimization

Plan coverage and capacity: frequency band implications, propagation expectations, antenna gain/tilt concepts, interference vs noise-limited thinking.
Triage poor radio KPIs: interpret symptoms consistent with SINR degradation, overload, or handover-edge conditions; select likely root causes.

Backhaul and transport engineering

Validate microwave/fiber links: build a defensible link budget, apply margins, and spot unrealistic power levels caused by dB math errors.
Maintain packet transport: recognize VLAN/MPLS/MTU failure patterns, congestion effects, and queueing impacts on real-time traffic.

Core network, voice, and signaling operations

Diagnose attach/call failures: identify where failures live (RAN vs core vs IMS), and distinguish signaling problems from bearer/QoS problems.
Interpret protocol behavior: map observed symptoms to the correct layer (e.g., routing vs session establishment vs media path).

NOC workflows and incident response

Correlate alarms to customer impact: reason from architecture boundaries (site, aggregation, core) to blast radius and likely service degradation type.
Prioritize corrective actions: choose actions that stabilize service first (capacity relief, reroutes, QoS enforcement) before deep optimization.

Provisioning and turn-up

Commission new sites/links: confirm duplexing assumptions, validate frequency plans, verify power levels, and ensure QoS markings/queues are consistent end-to-end.

Telecom Assessment FAQ: Interpreting RF, QoS, and Signaling Scenarios Correctly

When a scenario mentions “uplink” and “downlink,” what should I confirm before doing any math?

Confirm the duplexing method and the resource split. In FDD, uplink and downlink are separated by frequency (paired spectrum), so questions often hinge on the correct band pairing and duplex spacing. In TDD, uplink and downlink share the same frequency and are separated by time, so the frame pattern, guard periods, and synchronization/interference between neighboring cells become central to the correct answer.

How do I avoid blowing a link budget question with dB/dBm mistakes?

Keep everything in dB units until the very end. Treat dBm as an absolute power level and dB as a gain/loss you add or subtract. If the prompt combines transmitter power, antenna gains, feeder losses, and path loss, compute received power as an algebraic sum in dB. Convert to mW only if the question explicitly asks for linear power.

What’s the fastest way to decide whether an issue is RF, transport, or signaling?

Use a layered triage. RF issues typically present as degraded quality tied to geography, mobility, or channel conditions (coverage edge, fading, interference). Transport issues show up as increased latency/jitter/loss across multiple services or sites sharing a path. Signaling issues often present as “can’t attach,” “call setup fails,” or repeated retries/timeouts while basic IP connectivity may still work.

In QoS questions, what’s the most common trap?

Assuming that marking a packet guarantees priority. Markings (DSCP or 802.1p) only help if every hop maps that marking into the intended queue and the queue has appropriate scheduling and policing. Many scenarios are really testing whether you notice a remarking boundary, a mismatched policy, or congestion that starves a real-time queue despite correct classification.

I’m strong technically but miss points on “customer impact” or “what should you do first” items—how should I prepare?

Practice translating symptoms into outcomes: voice MOS degradation correlates with jitter/loss, data complaints during peak hours often correlate with contention and scheduling, and “no service” tends to imply access or backhaul failure. If you want to sharpen how you communicate findings and next steps to non-engineers (without losing technical accuracy), the Customer Service Soft Skills Quiz complements incident updates and escalation notes.

How should I think about telecom troubleshooting during outages or site access constraints?

Many real incidents impose safety, access, and coordination constraints (power failures, severe weather, restricted areas). The best technical answer is often the one that restores service while respecting constraints: stabilize power, restore backhaul, then optimize RF and QoS. For preparedness mindset and operational coordination patterns that often surface in telecom incident scenarios, the Workplace Emergency Preparedness Quiz is a useful cross-skill refresher.