(1/12) Which approach in Vue 3 might you use if you need to keep data in sync across multiple browser tabs or sessions, especially for offline usage?

---

• Use watchers for concurrency in main.js
• Use a plugin or composable that syncs reactive state with localStorage or IndexedDB (e.g., a pinia-plugin or a custom watchers approach)
• Define global watchers in defineExpose
• Impossible to sync data across tabs in Vue 3

(2/12) Which statement about watchers in a composable is correct if you want typed concurrency usage in a single file shared by multiple Vue 3 components?

---

• Inside the composable, define watch(...) referencing refs or computed passed by the components. Each usage creates watchers for that instance. If concurrency is needed, use onInvalidate in the watch callback
• Impossible to define watchers in a composable
• Use watchers in main.js for concurrency watchers only
• Use defineExpose for concurrency watchers

(3/12) In Vue 3, what is the preferred way to handle global error handling?

---

• Directly catching errors in every component
• config.errorHandler property on the app instance
• onGlobalError() lifecycle hook
• Vue 3 does not support global error handling

(4/12) What must you do if you need to import a third-party library only on the server side when using SSR in Vue 3?

---

• Place import statements inside onServerPrefetch exclusively
• Vue 3 does not support SSR with third-party libs
• Use dynamic import in your server entry file, or conditionally require it checking process.server (or equivalent) if using a framework like Nuxt 3
• Use watchers that run only on the server

(5/12) How do you convert a plain value or object into a ref if you’re not sure whether it’s already a ref in Vue 3?

---

• Use unref() repeatedly
• Use shallowRef always
• Use isRef() to check, then ref(...) if not a ref
• Use toRef() for arrays only

(6/12) Which approach might you use to convert a deeply nested object to a fully reactive structure in Vue 3 if you initially used markRaw() on it?

---

• Use watchers to manually track all properties
• Use unmarkRaw() function from 'vue'
• Create a new object and pass it to reactive() again without markRaw
• You cannot revert an object that was marked raw

(7/12) How can you define a route guard on an individual component using the Composition API in Vue 3 Router?

---

• Create watchers for route changes only
• Write a global directive in main.js
• Export an async function named beforeRouteEnter/beforeRouteLeave from the component, or use the composition-based addRouteGuard() if the router plugin is installed
• Use defineProps to check route params

(8/12) Which approach ensures watchers for concurrency are properly cleaned up if you create them inside a watchEffect in Vue 3?

---

• Define watchers in the watchEffect’s callback, but that could become complex. Typically, you either define watchers or watchEffect individually. If watchers are needed, define them outside. watchEffect can also handle concurrency with onInvalidate
• Impossible to define watchers inside watchEffect
• Use watchers in main.js for concurrency watchers only
• Use defineProps for concurrency watchers

(9/12) Which statement about server-side rendering (SSR) in Vue 3 is TRUE?

---

• Vue 3 provides an official @vue/server-renderer package for SSR
• You must use the 'vue-ssr-cli' command to enable SSR
• SSR is deprecated in Vue 3
• SSR only works if you disable reactivity entirely

(10/12) In Vue 3, if you want to have a transition effect when toggling between two components in the same view, which approach is correct?

---

• Wrap them in <transition> with a key on each component to differentiate them
• Use watchers to manually animate them
• Wrap them in <KeepAlive> only
• Transitions don’t support toggling components, only single elements

(11/12) Which statement about Vue 3’s Suspense feature is correct?

---

• It is used to handle asynchronous components and display fallback content
• It replaces the need for watchers and computed properties
• It only works with the Options API
• It works only with server-side rendering

(12/12) Which statement about the global error handler in Vue 3 is correct?

---

• You set it via app.config.errorHandler = (err, instance, info) => {...}
• You can only handle errors with onServerPrefetch
• Vue 3 does not have a global errorHandler
• You must define watchers in each component

Submit