Q: 10
HOTSPOT You need to develop a set of Web API’s for a company. What should you implement? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point. 
Your Answer
Discussion
Not seeing any need for Entity Types here. Functions, Actions, Complex Types. The key thing trips people up on these.
Functions, Actions, and Complex Types make sense for OData web APIs. Functions are for read-only ops, Actions can have side effects, Complex Types hold properties but no key. Pretty sure that's what Microsoft wants here. Disagree?
Pretty sure it's Functions, Actions, Complex Types. Functions are stateless and side-effect free, actions can change data, and complex types don't need keys. The question doesn’t mention unique IDs, so Entity Types seems off here. Let me know if I missed something.
Functions, Actions, Complex Types. Entity Types is a common trap for this kind of question since the scenario doesn't mention unique keys.
Nice, that's
Functions, Actions, and Complex Types.
Functions, Actions, and Complex Types.
For web APIs on Power Platform, do you guys pick Complex Types when there's no mention of unique keys? I was stuck between Entity Types and Complex Types since both come up in OData, but the lack of any key/identity requirement here made me lean toward Complex Types. Would that be right?
Why does Microsoft keep making this one so confusing? Functions, Actions, Complex Types is what I chose. No mention of needing keys anywhere, so Entity Types doesn't fit here I think.
Functions, Actions, Complex Types.
Yeah, Functions, Actions, Complex Types is what I'd pick here.
Pretty sure it's Complex Types over Entity Types here, since the question is about Web APIs and OData structure. Entity Types can be a trap answer because they need a key, while Complex Types don't.
Be respectful. No spam.
