Want more hot BPR News stories? Sign up for our morning blast HERE

“Asking the tough questions…”

Following a press conference where GOP nominee Donald Trump criticized the media as “disgusting,” CNN took to Twitter to promote a story where they asked the presidential candidate about the infamous gorilla incident that’s been grabbing headlines all week.

During the weekend, a 4-year-old boy fell into the gorilla habitat at the Cincinnati zoo, leaving the boy to be tossed around by the animal until it was eventually shot by zoo officials for fear he would further hurt the child.

Since the incident, outcry from leftists and animal rights activists has been that the shooting of the gorilla was racist, so CNN took the opportunity to ask Trump about it.

Here’s what CNN tweeted:

The tweet has Twitter users calling the network out for failing to ask Democratic front-runner Hillary Clinton tough questions, but asking Trump about the headline of the day.

Check it out:

.@CNN asking the tough questions — Zoe Camp (@jzcamp) May 31, 2016

THIS is why TRUMP calls you out …….. “@CNN: Would Donald Trump have killed the gorilla? https://t.co/W5UKbxkPRE pic.twitter.com/szFFWUT2ko” — Kenny Wallace (@Kenny_Wallace) May 31, 2016

.@CNN please sit down — Barrett Tryon (@btreports) May 31, 2016

https://twitter.com/RobProvince/status/737694116469964800

https://twitter.com/SullaBlack/status/737687308057600000

cnn has just given up… RT "@CNN: Would Donald Trump have killed the gorilla?" — ᴍɪᴋᴇ ᴛᴀᴅᴅᴏᴡ (@taddmike) May 31, 2016

https://twitter.com/GriffinGil12/status/737686951533281280

And you think this is a pertinent question for a serious news outlet? @CNN — Evan Cleaver (@EvanCleaver) May 31, 2016

– It's EXACTLY was CNN does.. Lie and spin!! I now only watch for entertainment value, ZERO credibility with EVERYTHING — Brian Reinert (@BrianReinert1) May 31, 2016

I mean, come on. — Mike Sharp (@Sharp208) May 31, 2016

https://twitter.com/matt_higginson/status/737690568852131840

https://twitter.com/Cherteapet/status/737686832436150272

Sign up for our morning blast HERE

CORRECTION: The age of the boy was incorrectly reported in earlier posts. It has been confirmed that the child is 3 and not 4-years-old.