Which statement is true about mapping a Resources folder as a drive?

Which statement is true about mapping a Resources folder as a drive?

• A. It can be mapped and shared among many users as a physical drive
• B. It cannot be shared
• C. It is read-only
• D. It must be on Amazon S3

Answer: (A)

Mapping a Resources folder as a drive presents that folder as a shared network location with a drive letter, so multiple users can access the same resources as if it were a local drive. This makes it easy for teams to reference the same transformers, scripts, and assets from a central place, ensuring consistency across workflows. It isn’t a physical drive; it’s a network-mapped path that relies on permissions to control access. It doesn’t have to be on Amazon S3—shared storage like a Windows file server or NAS can be used instead. The other statements don’t fit because sharing is possible with proper network permissions, the access mode depends on those permissions (so it’s not inherently read-only), and S3 is not a requirement.

Mapping a Resources folder as a drive presents that folder as a shared network location with a drive letter, so multiple users can access the same resources as if it were a local drive. This makes it easy for teams to reference the same transformers, scripts, and assets from a central place, ensuring consistency across workflows. It isn’t a physical drive; it’s a network-mapped path that relies on permissions to control access. It doesn’t have to be on Amazon S3—shared storage like a Windows file server or NAS can be used instead. The other statements don’t fit because sharing is possible with proper network permissions, the access mode depends on those permissions (so it’s not inherently read-only), and S3 is not a requirement.