Exam PL-300 topic 6 question 1 discussion

You wouldn't use composite for all. I would say import as the SQL Server data is only 2GB and excel is really small. Also, only need it refreshing once a day so this dataset is very small. Answer is A (Import)

Composite Model means now you can have a model, that very large tables of that are coming from the DirectQuery connection, without the need for importing, and small tables to be imported to be accessible quickly. In this case, Composite fits perfect. Source1 is 2GB, which is relatively too large for daily updates and way larger than Source2 which is only 5MB.

I would use Import storage mode. We only need to secure one refsh per day ("7 AM Pacific Time each day") so there is no need for a DirectQuery mode. Although Import would result in a larger Semantic model than using DirectQuery, SQL is "only" 2 Gb and, with Import mode, we will reach the "...fast response times when users interacts with a visualization" requirement

The correct answer is C- Composite because it is the only model that supports connections from multiple data sources

Near the real-time data is not required. 2GB size data seems large but it is the whole raw data, we need the latest 3 years data only here and we can pre-aggregate it. So, I prefer "A" which gives the highest speed and flexibility here.

A. Import The Import mode is the best choice here. This mode allows you to import the data into Power BI's memory, enabling fast response times when users interact with a visualization, which is one of the requirements. DirectQuery and Live Connection modes would not be suitable because they keep the data in the source system and query it from there, which can lead to slower response times. The Composite mode, which allows a combination of Import and DirectQuery, is not necessary here as there's no requirement to combine these two modes. Remember that with Import mode, you need to refresh the data to keep it up-to-date. The requirement is to have the report data current as of 7 AM Pacific Time each day, which can be achieved by scheduling a daily refresh in Power BI.

What about row level security, I believe it (RLS) does not work well with DirectQuery. (A)

2 different sources = Composite Model

C is the correct answer. I will go for the composite model. Bear in mind that the capacity for import mode is 1GB only.

how do you manage : The warehouse shipping department must be notified if the percentage of late orders within the current month exceeds 5%. in a full data import ? As far as I'm concerned, For that issue, I would put an alert on data change so tell me how you will put an alert in your "light for now" early morning import ? :-)

I had a hard time choosing between import and composite. Ultimately, what another user posted reminds us: the database is 2GB+ of text and growing. Do we want to be running a daily import on that? I think this is why the given answer is composite.

Source1 has a datasize of 2gb. The text does not specifically state that there is a premium capacity, so I suspect that the model size for an import model is 1GB. Is there a way to know how big this model size is?

Report data must be current as of 7 AM Pacific Time each day The reports must provide fast response times when users interact with a visualization

There are 2 sources. first is azure sql data base with 2GB of data and other one is excel 5 MB. You can not load 2GB of data in model hence you have to use direct query and excel we can import. Hence it is composite mode

Composite mode because it can mix Import and DirectQuery modes.

I think is Import. Because Direct query cannot fulfill this "Report data must be current as of 7 AM Pacific Time each day.", it will pull the latest lets say if it is 10AM, it will pull 10AM data right? Please correct me if I am wrong.

I also go for A. Import mode meets the requirements for fast response times and current data at 7 in the morning. Though the model must minimize the size of the dataset "as much as possible", it must meet the report and technical requirements. Fast response time is a hard requirement and it's sure that Import mode delivers that better than DirectQuery. I am no expert on Composite but I would argue that in the best case, it's as fast as Import mode. In Composite mode, some tables might switch to DirectQuery due to the user behaviour, but that would mean we would overachieve the requirement for daily refreshing, buying this overachievement through slower response time. That's not what we want. Future growth of the data is not to be considered in a question like this.