A newly hired Android developer learns that the app uses FileProvider to share files with other apps. They change the FileProvider paths configuration to path="." (root of internal storage). What security risk has been introduced?

• A.The path attribute in file_paths.xml scopes the directory tree the automatic backup agent walks, and it has no bearing on the content URIs a FileProvider grants, meaning the change affects the restore payload rather than the sharing surface the new developer worried about
• B.A path value of . fails XML validation inside the FileProvider initializer, and the app throws IllegalArgumentException on the first getUriForFile call, crashing before any file can be shared
• C.A path value of . is the hardened setting, pinning the provider to the application root and blocking the parent-directory traversal a crafted content URI would attempt
• D.path="." grants the FileProvider access to the entire internal storage root, meaning any file in the app's internal storage can be shared via a content URI - including sensitive databases, SharedPreferences XML files, and private keys