yoklainterview sim

Game Development Ue Blueprint Cpp Interop Interview Questions

75 verified Game Development Ue Blueprint Cpp Interop interview questions — solve with answers, learn from explanations, test yourself in a real simulation.

Try the real simulation →

Sample questions

Ue Blueprint Cpp InteropDifficulty 1
In Unreal C++, what does marking a UFUNCTION with BlueprintCallable do?
  • aForces the function to run on a background thread
  • bLets it be called as a node in a Blueprint graph
  • cAutomatically replicates the function call to all clients
  • dMarks the function as required for the class to compile
Explanation:BlueprintCallable exposes the C++ function so it can be dragged into a Blueprint or Level Blueprint graph and executed from there.
Ue Blueprint Cpp InteropDifficulty 2
A UFUNCTION is marked BlueprintPure instead of plain BlueprintCallable. What is the visible difference in the Blueprint graph node?
  • aThe node gets a red border to warn about performance
  • bThe node can only be placed inside a Function Blueprint
  • cThe node has no exec pins, only data pins
  • dThe node is hidden from the Blueprint palette by default
Explanation:BlueprintPure marks the function as not affecting the owning object, so its Blueprint node is rendered without exec pins — it is wired purely through data pins.
Ue Blueprint Cpp InteropDifficulty 2
UFUNCTION(BlueprintImplementableEvent)
void OnObjectiveCompleted();

This declaration has no C++ definition anywhere in the source. Why does the module still compile and link?
  • aThe function body is meant to live entirely in a Blueprint graph, not in C++
  • bThe linker silently generates an empty stub for any undefined UFUNCTION
  • cUFUNCTION declarations without a body are optional and get skipped by the compiler
  • dThe function is treated as pure virtual, so subclasses must define it
Explanation:BlueprintImplementableEvent declares a function whose implementation is provided in a Blueprint graph; giving it a C++ body is not expected, and the generated code calls into the Blueprint implementation instead.
Ue Blueprint Cpp InteropDifficulty 2
UFUNCTION(BlueprintNativeEvent)
void OnPickup(AActor* Instigator);

Where should the default C++ logic for OnPickup be written?
  • aDirectly inside the body of OnPickup in the header
  • bIn a separate function named OnPickup_Default
  • cIn the constructor of the owning class
  • dIn a function named OnPickup_Implementation
Explanation:For BlueprintNativeEvent, Unreal Header Tool expects the native default logic in a function with the same name plus _Implementation; the generated wrapper calls it when no Blueprint override exists.
Ue Blueprint Cpp InteropDifficulty 2
UFUNCTION()
void InternalRecalculate();

This UFUNCTION has no Blueprint-related specifiers. What follows for Blueprint graphs?
  • aIt appears in the Blueprint palette but greyed out until enabled
  • bIt cannot be dragged into a Blueprint graph as a callable node
  • cIt becomes a BlueprintPure node automatically since it takes no parameters
  • dIt is exposed to Blueprint but only inside the function's own class
Explanation:A bare UFUNCTION() is still reflected (useful for things like console commands or delegate binding), but without BlueprintCallable, BlueprintPure, or an event specifier it does not show up as a usable node in a Blueprint graph.
Ue Blueprint Cpp InteropDifficulty 1
What does the CallInEditor specifier add to a UFUNCTION?
  • aA button in the Details panel that runs it on selected instances
  • bAutomatic execution of the function once when the editor starts up
  • cA console command that can be typed into the in-editor output log
  • dA menu entry under the Blueprint graph's right-click context menu
Explanation:CallInEditor makes the function callable from a button shown in the Details panel for selected instances, without needing Play mode.

Test yourself against the 2850-question Game Development bank.

Start interview