引導式測驗 · 中等 等級
智慧路燈與城市感測器網路測驗
了解智慧路燈可以收集什麼、城市如何區分維護和監控,以及為什麼透明的政策和審計很重要。
問題 1 的 8
Which details should a city disclose about a networked streetlight system?
預覽每個問題8 問題
當您參加測驗時,就會出現答案和解釋。
- Which details should a city disclose about a networked streetlight system?
- Identify each sensor, its purpose, and the data it collects
- Assume the equipment only monitors bulb status
- Treat all sensor data as anonymous
- Use collected information for any municipal purpose
- Why distinguish maintenance monitoring from surveillance use?
- Lighting data cannot be shared
- Surveillance features are identical to outage sensors
- Different purposes can require different safeguards and permissions
- Maintenance automatically authorizes police access
- What does San Diego’s streetlight example illustrate?
- A universal design used by every city
- A local system with public use policies and reporting
- A guarantee that streetlight data are never sensitive
- A rule that all cities must use cameras
- What can audit logs help oversight staff examine?
- The exact intent of every person recorded
- Whether a camera captures every event
- How many bulbs are installed
- Who accessed data and whether use followed policy
- Why should cities set retention limits?
- Stored images or movement data can expose people and routines
- Retention makes sensors more accurate
- Longer retention removes privacy concerns
- Streetlight data contain no location information
- What security measure helps protect a sensor network?
- One shared password for every device
- Public access to maintenance accounts
- Device identity, patching, network segmentation, and access logging
- Disabling software updates
- When should a city consider public input?
- Only after a breach occurs
- Before acquisition or expansion that changes data collection or use
- Only when changing streetlight color
- Never, if the vendor has a privacy policy
- How should surveillance capability be governed?
- By whatever uses the hardware can technically support
- By vendor defaults alone
- Without documentation to preserve flexibility
- By explicit approved purposes, access rules, audits, and oversight