To clarify a bit, SPF and DKIM are how you take responsibility for a particular message (SPF by sending IP and DKIM by digital signature) and DMARC is how you tell recipients what to do when a message is not authenticated.
Technically SPF has a negative action, but the reality is most recipients ignore it and focus on the positive signal.
DKIM has no negative action, a message is either signed and validated or not, but you cannot make any assumptions about messages being signed until you get to DMARC.
DMARC is a way to express to the world that you are authenticating all messages (in practice with SPF and/or DKIM, although other mechanisms can be used with private arrangement or future protocol development), and also to suggest what should happen to unauthenticated messages. You can request recipients quarantine or reject, although this is just a request. You can also request automated feedback reports to help you understand when your domain is spoofed (legitimately or not, even just forwarding can cause a message to become unauthenticated).
There is more to it, in particular domain alignment (the From header vs the RFC5321.Mail command) and signing details come into play with DMARC.
In short though, do your best to deploy SPF and DKIM as these help you build a positive reputation so that receiving servers are more likely to place your mail into the Inbox if they can build a reputation score. Assuming your mail is wanted by recipients.
I would not recommend deploying DMARC in quarantine/reject mode unless you have a compelling reason to do so, or unless you use reporting mode for several weeks and understand what failures are occurring.