Effect of Infrastructure as a Code on Deployment Time (minutes)

Infrastructure as Code (IaC) significantly reduces deployment time, as evidenced by the descriptive
statistics and inferential analysis presented. The descriptive statistics reveal that tasks took an average
of 41.10 minutes when deploying on Microsoft Azure. However, when comparing the deployment times
between those who used IaC and those who adopted a manual approach, a notable difference emerges.
Figure 46 illustrates this discrepancy, showing that participants who utilized IaC experienced shorter
deployment times compared to those who did not.

Furthermore, the inferential analysis, specifically the t-test, provides statistical evidence supporting the
impact of IaC on deployment time. The mean difference in deployment time between the two groups
was 15.172 minutes, with a p-value less than 0.001, indicating a highly significant difference. It provides
an instance of Infrastructure as Code (IaC) that significantly accelerates the deployment process,
enabling timely implementation of infrastructure provisioning.
Current papers on this topic have implicitly affirmed that Infrastructure as Code (IaC)
contributes to deployment efficiency. According to research, the utilization of code-based
infrastructure occupation decreased the time required for deployment and enhanced the
operational process. According to Mahmood and Chang (2022), automating repetitive procedures
and standardizing deployment processes can reduce the need for manual interventions, resulting
in a faster code distribution to workloads. Consequently, an enterprise's capacity to expedite the
release of apps and services to the market would enhance in comparison to other establishments,
thereby achieving a competitive advantage in the fast-paced commercial environment.

Effect of Infrastructure as a Code on Deployment Perceived Ease of Use (1-10)

The process of utilizing infrastructure using Infrastructure as Code (IaC) highly impacts the way how
infrastructure is perceived, in terms of ease of use. The mean difference in perceived easiness of use
between respondents (who implemented IaC) and (who employed manual approach) resulted in -2.636
units on a Likert scale of 1-10, and this obtained with a p-value of less than 0.001. Such an ability
therefore shows a considerable users' contentment stimulated by composing infrastructure in
automated mode.

It is clear from table 6 that the users who came under IaC scoring reported higher scores at perceived
ease of use compared to those who did not. Another study would be carried out among participant 2, 4,
5, 6, 8, 10, 12, 14, 15, 17, and 19 that have IaC. The result displayed an easy of use 7 and above among
the participants. However, the user ratings of IaC experienced also distinctions as one range of
participants who didn't use IaC literate highly experienced difficulties by attaining a score below 6.

The above figure 46 is a further visualization of the same facts. This time, we are comparing the
experience level in cloud computing as well as the preference for IaC. The migration paves way for
establishing a defined employment relationship while paving way for the people in the low to moderate
experienced group that clearly show a clear strength in adopting the infrastructure as a code(IaC )
feature awarding a high ease of use score during the usage of the IaC.

Literature acknowledges these results, emphasizing on how International Automotive Consortium(IaC)

improves the user experience and deployment ease. On the one hand, a study by Thiyagarajan [Link].
(2022) and another by Chijioke-Uche (2022) conclusively show that IaC drastically simplifies deployment,
reduces complexity and at the same time, making cloud infrastructure more user friendly. Through their
work, this is the example that automated provisioning and configuration tasks for IaC make it possible
for organizations to have a scalable and agile provision, while their operational costs are being
minimized. Furthermore, this increases a collaborative environment, standardized processes across
accounts, and compliance with industry regulations. Such insights, therefore, attest as to how IaC has
the greatest impact on cloud infrastructure management through smoothness, efficiency, and
adherence to standards in multiple surrounding systems.

Effect of Infrastructure as a Code on Deployment Error Rate (%)

Infrastructure as Code, IaC, serves as the primary way to decrease the checkout rate of programming
errors. The fieldwork dataset illuminates varying error run ups noted along the participants progress,
from 1% to 12%. The unique display that the crosstab gives is remarkable when referencing the cross
tabulation of experience and IaC preferences in cloud environment deployment (Table 7). Among the
sample, the individuals who put IaC into use demonstrated negligible mistakes to the hist of those who
chose to continue applying manual procedures.

Furthermore, the values shown in table 8 below also highlight the imposition of IaC on error reduction.
Among participants who concentrated on the application of IaC, the mean error rate was 3.2%, which is
impressively lower than the 8.6% recorded on manuals achers. The difference in error rates clearly
stands for the accuracy of IaC that is used as a way to increase the efficiency and stability of deploying
operations.

The findings also literature them up, which brings out the pros of IaC in decreasing the chance for
deployment mistakes. The work of Guerriero et al. (2019) revealed that across the sector- the
organizations that used IaC or stands for Infrastructure as a Code , experienced 60% lower failure rates
and 90% faster recovery times compared to traditional manual methods. On the other side Rajapakse et
al, (2020) noted a dramatic decline of error rates throughout IaC implementation phases which were
considered highly instrumental in making systems stronger and even more resilient.

Effect of Infrastructure as a Code on Deployment Consistency Rate (%)

The consistent deployments as demonstrated in Infrastructure as Code become much evident as the
data in Table 8 shows improved deployment accuracy by -6.778% (P-value < 0.001). It simply means that
we can now expect enhanced homogeneity and consistency in raising software standards in the whole
gamut of environment. Descriptive statistics demonstrate that generally the mean consistency rate for
deployments under Infrastructure as Code pattern is significantly higher than across the board in
deployments employing manual approaches. For infrastructure as code deployment the estimated
consistency rate is 91.95% (SD = 0.936), however, for manual deployments this may be lower, but exact
figures for manual deployments are not provided.
Moreover, chart 46 showcases the distinction between preferences in cloud computing and experience
for Infrastructure “as Code” shown in the next figure. The tendency to these individuals of who have low
and moderate cloud computing experience or they use infrastructure automation in their networking is
shown by this trend. It is exactly what Bali & Walia's previous study (2023) pointed out, of which
Infrastructure as Code brought the improvement that no team members have to worry about
deployment consistency and reliability any more. The research results state that Infrastructure as Code
facilitates the deployment process by decoupling configurations from platforms and, consequently,
minimizes the possibility of configuration inconsistencies and errors. The cause behind the development
of consistency is automation itself that is characteristic of Infrastructure as Code, allowing generating
exact replications of the deployment configurations, which makes the whole deployment process more
reliable and accurate.

Effect of Infrastructure as a Code on Deployment Task Success Rate (%)

Infrastructure as Code significantly increases deployment task success rates, with a mean difference of -
7.232% (p < 0.001), indicating a higher likelihood of successful completion of deployment tasks. The
descriptive statistics provided in Table 6 illustrate that participants who utilized Infrastructure as Code
achieved higher task success rates compared to those who adopted a manual approach. For instance,
participants with moderate and high levels of cloud computing experience, who employed IaC,
demonstrated task success rates of 95% and 96%, respectively, as shown in Figure 46.

This improvement in task success rate can be attributed to several factors. Firstly, Infrastructure as Code
promotes consistency and repeatability in deployment processes, minimizing human error and ensuring
configurations are standardized across environments. As depicted in Table 8, the consistency rate for IaC
users was notably higher at 91.95% compared to manual deployment. IaC automation streamlines
deployment operations, saving time and effort while provisioning infrastructure. On average, IaC
users deploy in 41.10 minutes, compared to 48.60 minutes for manual deployment (Table 8).
Studies confirm that Infrastructure as Code improves deployment success rates. Guerriero et al.
(2020) found that IaC reduced deployment failures and downtime. Murphy (2022) observed that
IaC adoption increased operational efficiency, system dependability, and task success. Thus,
integrating Infrastructure as Code into cloud infrastructure deployment processes improves
operational efficiency, project delivery, and customer happiness.