Sometimes you can use technology without having to understand it. You can use put together a solution using HTTP without having to understand the entire protocol stack under it. You can create some small service using an scripting language without having to learn algorithms or data structures, memory management, multi-threading, etc.

But when things do not work, and you are required to do retrospectives and post-mortems detailing why things break, and when you are required to mitigate risks from things breaking again... that's when you can no longer get away with simply seeing yourself as a someone abstracted from the low-level stuff. You will now have to understand things, and if you don't, your organization will find someone else that will.