Which feature does the service worker file enable?

Which feature does the service worker file enable?

• A. Automatic updates of dependencies
• B. Error handling during builds
• C. Offline capability through caching
• D. Code splitting

Answer: (C)

Service workers unlock offline capability through caching. A service worker runs separately from the web page and can intercept network requests, so it can pre-cache essential assets during installation and then serve those cached files when the user is offline. This means the app can load and function even without a network connection, which is the core benefit of using a service worker. It can also implement smart caching strategies, deciding when to fetch fresh data from the network and when to rely on cached responses. The other items aren’t features of the service worker: updating dependencies automatically is something managed by package managers and build tools, error handling during builds is a build-time concern, and code splitting is a bundling/optimization technique not provided by service workers.

Service workers unlock offline capability through caching. A service worker runs separately from the web page and can intercept network requests, so it can pre-cache essential assets during installation and then serve those cached files when the user is offline. This means the app can load and function even without a network connection, which is the core benefit of using a service worker. It can also implement smart caching strategies, deciding when to fetch fresh data from the network and when to rely on cached responses. The other items aren’t features of the service worker: updating dependencies automatically is something managed by package managers and build tools, error handling during builds is a build-time concern, and code splitting is a bundling/optimization technique not provided by service workers.