Does enabling table attachments minimize Dataverse storage?
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. A company uses Dataverse. The company plans to store and manage documents and data in the environment. The company requires a solution that minimizes Dataverse storage consumption. You need to recommend a solution. Solution: Enable attachments for a table. Does the solution meet the goal?
Community Votes
100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
Tests whether you know Dataverse table attachments consume internal file capacity, not external storage; the trap is assuming attachments are lightweight or stored outside Dataverse.
Enabling attachments on a Dataverse table stores files inside Dataverse, increasing file storage consumption rather than minimizing it. This page confirms the solution does not meet the goal and explains why SharePoint integration is the recommended approach.
Choosing 'Yes' because attachments seem like a low-cost feature, but Dataverse attachments (notes) count against the environment's file storage capacity and increase consumption.
Community Discussion (3 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Enabling attachments for a table stores the attached files directly inside Dataverse as note attachments, which consumes the environment's file storage capacity. The requirement is to minimize Dataverse storage consumption, so adding more internal file storage works against that goal. Microsoft's guidance is to use SharePoint integration for document management so files live in SharePoint and Dataverse stores only a reference. As killionb12 noted, "Enabling attachments for a table will actually increase Dataverse storage consumption" because attachments are stored within Dataverse. Therefore the solution does not meet the goal, and the correct answer is No (B).Why the Other Options Are Wrong
Option A ("Yes") is incorrect because it assumes attachments reduce the Dataverse footprint, but attachments are stored within the Dataverse environment and count against file capacity. There is no third option, and the only alternative to No is Yes, which directly contradicts the stated requirement to minimize Dataverse storage. Choosing Yes would ignore how Dataverse capacity is billed and allocated.Community Comment Notes
Commenters unanimously selected No. killionb12 explained that attachments increase Dataverse storage and suggested SharePoint integration for document management. examtopicss1122 agreed, saying "Enabling attachments for tables means that the system requires more space" and that SharePoint integration stores only a reference in Dataverse. Another learner simply confirmed "Correct." These views align with the official Microsoft recommendation.Official Reference
Exam Strategy
In PL-200 scenario questions, always identify where the data physically resides: Dataverse internal storage (database, file, log) versus an external service like SharePoint. If the goal is to minimize Dataverse storage, select options that move documents out of Dataverse and keep only references.
Frequently Asked Questions
Why does enabling table attachments increase Dataverse storage?
Attachments are stored in the Dataverse environment and consume file storage capacity, so they add to usage instead of reducing it.
What is the recommended way to minimize Dataverse storage for documents?
Use SharePoint integration so documents remain in SharePoint and Dataverse stores only a reference to each document.