Search the practice set
275 questions, 991 terms and 600 topics in 30 areas.
30 results for “Device Provisioning”
Zero Touch Provisioning
A device obtaining its identity and configuration on first boot without a human configuring it, which is the only approach that scales past a few hundred units.
Device Group Rollout
Applying configuration or firmware to a fleet in ordered cohorts with health checks between them, because a bad change applied to everything at once has no remedy.
Provisioning Self-Service
Teams obtaining infrastructure without a ticket, within bounds that make the request safe by construction rather than by review.
Test Data Provisioning
Getting each test the data it needs, in a state it can rely on, without copying production personal data into a weaker environment.
A/B Partition Update
Writing firmware to an inactive partition and switching on next boot, so a failed update falls back to the previous image rather than bricking the device.
Client Runtime Constraint
The properties of the browser or device you do not control — CPU, network, version, extensions — which make the client a distributed system component rather than a rendering surface.
Clock Drift
Device clocks diverging from real time, which corrupts ordering, expires certificates early or late, and produces data that appears to arrive from the past.
Compute Tier Placement
Deciding which of on-device, on-premises, metro, regional or central compute a workload belongs to, from its latency, data volume and autonomy requirements.
Edge Aggregation
Summarising or filtering telemetry at the device or gateway so that only what is needed leaves, which is usually the difference between a viable and an unaffordable design.
Hardware Backed Credential
A private key generated inside a secure element and unable to leave it, so device identity cannot be copied off the device.
Hardware Security Module
A tamper-resistant device that generates and stores keys and performs cryptographic operations without the key material ever being extractable.
Managed Service
A capability the provider operates — provisioning, patching, backup, scaling and failover — leaving you the configuration and the data.
N+1 and 2N Redundancy
Provisioning one spare beyond required capacity versus provisioning double, and the failure assumptions each encodes.
NAT Gateway
A managed device that lets instances in a private subnet make outbound connections without being reachable inbound.
Port Exhaustion
Running out of available source ports for outbound connections through a NAT device, causing new connections to fail while everything appears healthy.
Pre-Scaling
Provisioning capacity in advance of a known traffic event rather than relying on autoscaling to react to it.
Reported Versus Desired State
Holding two representations of a device — what it last said it was, and what it should be — with the gap between them driving reconciliation.
An OTA firmware update has bricked 3% of a 50,000-device fleet. What do you do, and what should have prevented it?
Halt immediately, then determine the correlation Stop the rollout before anything else. Then find what the 1,500 have in common: hardware revision, previous fir
You inherit an IoT fleet of 80,000 devices whose client certificates all expire in fourteen months. What do you do?
Establish whether rotation is even possible The first question is whether the current firmware can obtain and install a new certificate remotely. If it cannot,
Your platform team is now a ticket queue — every environment, every permission, every new service goes through them. How do you get out of it?
Categorise the queue before automating anything Take a month of tickets and group them. The distribution is always uneven, and two or three categories are usual
Device Provisioning
Getting identity and configuration onto hardware at manufacture or first boot.
Device Identity
Identifying a thing rather than a person, and rotating a credential you cannot type.
Device Telemetry at Scale
Deciding what a device sends, how often, and what is aggregated before it leaves.
Self-Service Provisioning
Teams getting infrastructure without a ticket, and the guardrails that make that safe.
Client Feature Flags
Flag evaluation on a device you do not control, and the flicker and staleness it brings.
Cost Allocation
Tagging enforced at provisioning, and apportioning shared costs.
Edge Compute Topologies
Regional, metro, on-premises and on-device, and what each tier is genuinely for.
Edge Security & Attestation
Secure boot, hardware roots of trust, and proving what is running on a device.
OTA Updates
Updating firmware over a flaky link, with rollback, and without bricking the device.