Why Do We Use Text Data Formats? (CCNA Automation & DevNet Guide)(200-901) - Post 2

 

Why Do We Use Text Data Formats? (CCNA Automation Beginner Guide (200-901))


If you are learning Automation (DevNet), one of the first concepts you must understand is text data formats.

Modern networks are no longer configured only with CLI commands. Today, routers, switches, controllers, APIs, cloud platforms, and automation tools constantly exchange structured data.

But here’s the big question:

👉 Why can’t applications just send raw data?

The answer is simple: computers need structure to understand information.

In this guide, you’ll learn:

  • Why data formats are necessary

  • How structured data works

  • What key-value pairs are

  • What serialization and parsing mean

  • Why XML, JSON, and YAML are future-proof

This is foundational knowledge for every CCNA Automation student.


language as a data format.
language as a data format.



Why Do We Need Data Formats?

When humans communicate, we follow rules.

We speak a common language.
We structure sentences properly.
We use grammar.
We start conversations with greetings.

Language itself is a format.

Think about it this way:

Your thoughts are data inside your brain.
You cannot send thoughts directly to someone.
You must convert them into a shared language like English.

That process is similar to what happens in networking.

When applications communicate, they also need a common format. Without it, they cannot understand each other.

If two people speak different languages, communication fails.

The same thing happens between software applications.


People communicating without using a common language.
 People communicating without using a common language.


What Happens Without a Data Format?

Imagine an application sends this information:


encapsulation
encapsulation


Where does the interface name end?
Where does the IP address start?
What is the description?

Humans can guess.

Computers cannot.

Applications need exact rules that define:

  • Where data begins

  • Where it ends

  • What each value represents

That is why we use structured data formats like:

  • XML

  • JSON


Sending data without data format.
Sending data without data format.



Apps communicate using XML data format.
Apps communicate using XML data format.



How Do Data Formats Work?

Every data format defines two things:

1️⃣ Structure

Structure defines how information is organized.

Example:
An interface has:

  • Name

  • IP address

  • Description

The structure decides where each piece belongs.


2️⃣ Syntax

Syntax defines the characters and symbols used.

For example:

  • XML uses tags <interface>

  • JSON uses { }, quotes, and colons

  • YAML uses indentation

  • CSV uses commas

The information stays the same.
Only the wrapping format changes.

XML, JSON and YAML structure and syntax example.
XML, JSON and YAML structure and syntax example.


Most beginners find YAML easiest to read.

That is why it is widely used in:

  • Ansible

  • Kubernetes

  • DevOps tools


Understanding Key-Value Pairs (Very Important!)

This is the most important concept in CCNA Automation.

A key-value pair means:

  • The key is the label

  • The value is the data



Example:
Example:

Without the key, the number 75 means nothing.

Is it temperature?
Is it CPU usage?
Is it interface speed?

The key gives meaning to the value.

In automation:

👉 Data without keys is useless.

All structured formats (XML, JSON, YAML) are built on key-value pairs.

Label and Box pair.
Label and Box pair







Cisco CLI:
Cisco CLI:



XML
XML format

JSON
JSON format



YAML
YAML format


What Is Serialization and Parsing in Automation?

Now let’s connect this to programming.

Applications store data in memory as objects.

When they need to:

  • Save it

  • Send it over a network

  • Store it in a file

They must convert it into text format.

This process is called:

Serialization

Converting data → into text format (JSON/XML/YAML)



Serialization and Parsing example.
Serialization and Parsing example.


When receiving data:

Parsing

Reading text → converting it back into usable program data


In simple terms:

  • Serialization = Data → Text

  • Parsing = Text → Data

These are core skills in Python-based automation.

Common Problems with Data Formats in Automation

Text formats are powerful, but strict.

Common issues:

  • Missing comma in JSON → breaks parser

  • Wrong indentation in YAML → breaks file

  • Missing closing tag in XML → invalid file

  • CSV values containing commas → format errors

Always validate your files.

Many DevNet exam questions are based on incorrect formatting examples.


Why Are Text Data Formats Future-Proof related to CCNA automation?

Text formats are not tied to any programming language.

Every major language supports them:

  • Python

  • Java

  • C++

  • Go

  • JavaScript

They integrate with:

  • Git

  • CI/CD pipelines

  • Cloud tools

  • DevOps workflows

That makes them universal and future-ready.



Data Formats are future-proof.
Data Formats are future-proof.


Why This Matters for CCNA Automation

If you want to succeed in:

  • CCNA Automation

  • DevNet Associate

  • Network Automation roles

  • Infrastructure as Code

You must understand:

  • Key-value structure

  • XML

  • JSON

  • YAML

  • Serialization

  • Parsing

This is the foundation of modern networking.

Without structured data, automation does not exist.


#CCNAAutomation
#DevNet
#NetworkAutomation
#JSON
#XML
#YAML
#PythonNetworking
#AutomationBasics
#NetDevOps
#DataFormats


Data Formats: click here

Featured Post

Day 41 — BGP Confederations: Sub-AS Design, External View and Migration

1. Opening Confederations are another way to scale BGP inside a large administrative domain. They divide the domain into member autonomous systems while presenting a single confederation identifier to external peers. They are powerful, but their operational model is more complex than simply 'using private ASNs inside.' The engineering goal is not to memorize another BGP command. It is to understand what information each speaker is allowed to propagate, what path information can be hidden, and what failure domain is created by the chosen control-plane architecture . 2. Concept and standards behavior RFC 5065 defines AS_CONFED_SEQUENCE and AS_CONFED_SET and how member-AS relationships are represented. Confederation external sessions have eBGP-like properties inside the confederation, while the confederation is presented externally as one AS. Modern guidance must also account for the fact that RFC 9774 prohibits new origination of AS_SET/AS_CONFED_SET in ordinary aggregation c...