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)
you missed this detail : The warehouse shipping department must be notified if the percentage of late orders within the current month exceeds 5%..
How do you put an alert then ?
I worked with DBs that are much larger than 5GB and have always used import due to fast response/RLS/Time Intelligence etc...There are a few ways to limit the dataset size, most common is to use SQL with Where clause to limit the data to only that you needed or if you don't use/don't know SQL, do a transform before loading the data. I would do an import in this case but my answer will not be neccessarily the correct answer that Microsoft wanted.
I think the size of the data is 2GB in the database though not Vertipaq compressed. 1GB limitation applies to size of the pbix file which is already compressed and will be significantly less than raw data.
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.
The answer is C composite mode which means a combination of Direct Query and Import mode. Remember in this model there is a many-to-many relationship between the Sales Employee table and the Orders table. ( See previous question in the previous page)and this kind of relationship (many-to-many) is always used in a composite model.
A "composite model" in Power BI is a data model that allows you to combine data from multiple sources, including both imported data and data accessed directly through Direct Query (live connection to a database), within a single model, enabling you to create relationships and build reports using data from different origins simultaneously; essentially, it lets you mix and match data storage modes for optimal performance depending on the source data.
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
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.
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?
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
You can if you have PRO or PREMIUM license. On technical requirements they mentioned that the reports must be store in a single Power BI workspace so we can assume that the company have any of each license. The best option is Import mode
This section is not available anymore. Please use the main Exam Page.PL-300 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Mizaan
Highly Voted 2 years, 6 months agodesibaby09
4 months, 2 weeks agoDani_eL
1 year, 1 month agoNawabi
2 years, 2 months agopowerbibuddy
2 years, 5 months agoSmyrol
10 months agoLeeTheRed
1 year, 4 months agomsexamkiller
2 years, 4 months agoshakes103
Highly Voted 2 years, 5 months agoSylUK
Most Recent 2 months agoSylUK
2 months ago_jay95_
3 months agojaume
5 months agoLuluSkyy
6 months, 1 week agoHenryBiz
10 months, 2 weeks agoe3ddceb
11 months, 2 weeks ago9f73003
1 year agoJudT
1 year agoJudT
1 year agoDani_eL
1 year, 1 month ago28485e1
1 year, 1 month agoOnbekend
1 year, 2 months agoJohnChung
1 year, 2 months agoMandar77
1 year, 5 months ago5bf040d
1 month agojanojano
1 year, 6 months ago