This is an issue that your project manager, team leader, product owner or scrum master ought to be ensuring isn't happening.
Ideally, all tasks that belong to a team should be able to be picked up and completed by any member of that team who has the technical capability, regardless of their level or experience. (e.g. all software engineers should understand all the development tasks, all platform engineers should understand all the devops tasks, etc.)
When any team member speaks out in a team ceremony to trivialise a task, what they're really doing is preventing others in the team from being able to estimate it properly and therefore also making it harder for others to pick up that task because they've subverted the important discussion which would otherwise get into the detail of that task. It leads to potential misunderstandings with some in the team remaining in the dark about exactly what work is involved, and also leads to estimates being produced which don't have the full support or buy-in of the entire team.
The fact that some team members may have less experience should not mean that those people are left in the dark when it comes to understanding the work needed, nor that they shouldn't be involved in agreeing to estimates.
If a team is producing estimates which don't have the buy-in of those doing the work, then the whole team has a problem - Clearly, from a project/team management point of view, this is not a good situation to be in, so when it happens it means that the team as a whole has an opportunity to improve, and this should be driven by the team, but also by team/project/product leadership where possible.
One approach if you hear this happen in a ceremony is to ask for more detail from whoever calls out how easy the task is -- asking a direct question to that person along the lines of "Could you explain and elaborate on that so that I can understand the estimate?" or "What would you do to complete the task?", or even ask that their name is mentioned on the task in the context of "Speak to bob for more information" (So that someone else picking up the task knows who to go to when they need to find out what to do)
It is typically in the best interests of the Project Manager and Product Owner to ensure that everybody in a team buys-in to estimates and understands the work which needs doing. Ideally, those people should be proactively making sure that you aren't alone in needing to "battle" for others to explain what work needs to happen.
There are benefits in ensuring this doesn't happen - when that everybody in the team has a shared understanding of the work involved in a task, it allows greater collaboration and sharing of ideas during planning; a senior engineer will not necessarily always get the right estimate each time, and they may still miss out important detail or misunderstand it themselves, perhaps forgetting some of the effort (For example, time to set up their environment, impact on testing, a need to define test data/scenarios, configuration, deployment, etc.)