100 ColdFusion Interview Questions

Last updated - 8 August 2022

Topic 1 – COLDFUSION versions

Q1.What are the differences between the different versions of the coldfusion?
Before CF6 MX coldfusion was implemented in Microsoft Visual C++.
CF6 MX
Coldfusion was rebuild by using JAVA EE platform.
CF 7 MX                                              
-  Addition of the Coldfusion Gateways
-  Support for the MAC OS
-  CFC

Coldfusion 8
-  Few tags have been added and enhanced
CFPDF,CFPRESENTATION,CFZIP,CFEXCHANGE,CAPTCHA generation enhancement using CFIMAGE

Coldfusion 9
- New tags CFFINALLY,CFCONTINUE
- ORM like hibernate in JAVA
- Server.CFC file with onServerStart () and onServerEnd() methods

Coldfusion 10 (Zeus)
- Enhencements in Scheduler, webservices ,Security,HTML5,ORM features

Coldfusion 11 (Splendor)
- Mobile development and chart engine changes using Zing Chart previously it was using webChart engine for chart generation
- CFHTMLTOPDF

Adobe ColdFusion (2016 release)

Adobe ColdFusion (2016 release), Codenamed: Raijin (and also known generically as ColdFusion 2016) was released on February 16, 2016.

New or improved features available in all editions (Standard, Enterprise, and Developer) include:

  • Language enhancements
  • Command Line Interface (CLI)
  • PDF generation enhancements
  • Security enhancements
  • External session storage (Redis)
  • Swagger document generation
  • NTLM support
  • API Manager

Adobe ColdFusion (2018 Release)

Adobe ColdFusion (2018 release), known generically as ColdFusion 2018, was released on July 12, 2018.ColdFusion 2018 was codenamed Aether during prerelease.

As of July 2020, Adobe had released 10 updates for ColdFusion 2018.

New or improved features available in all editions (Standard, Enterprise, and Developer) include:

  • Language enhancements (including NULL, abstract classes and methods, covariants and finals, closures in tags, and more)
  • Asynchronous programming, using Futures
  • Command line REPL
  • Auto lockdown capability
  • Distributed cache support (Redis, memcached, JCS)
  • REST playground capability
  • Modernized Admin UI
  • Performance Monitoring Toolset

Adobe ColdFusion (2021 Release)

Adobe ColdFusion (2021 Release) was released on Nov 11th, 2020. ColdFusion 2021 was code named Project Stratus during pre-release.

New or improved features available in all editions (Standard, Enterprise, and Developer) include:

  • Lightweight installer
  • ColdFusion Package Manager
  • Cloud storage services
  • Messaging services
  • No-SQL database
  • Single sign-on
  • Core language changes
  • Performance Monitoring Tool set

References –

Topic 2 – Coldfusion Architecture

Q1.  Explain coldfusion architecture?

ColdFusion is a rapid application development environment that lets you build dynamic websites and Internet applications quickly and easily.

ColdFusion consists of the following core elements:
·         CFScript Engine
·         CFML
·         ColdFusion Administrator
·         Verity Search Engine
·         Extensions

1. CFScript Engine
Coldfusion includes a built-in scripting language, CFScript, that let us write code in a
JavaScript fashion.

2.       ColdFusion Markup Language   
ColdFusion Markup Language (CFML) is a tag-based language, similar to HTML, that uses special tags and
Functions.

3.       Coldfusion Administrator
ColdFusion Administrator configures and manages the ColdFusion application server. It is a secure web-based application like control panel that you can access using any web browser, from any computer with an Internet connection.

4.       Verity search Engine -
The Verity Search Server (also called the Verity search engine) provides full text search capability for documents and data on a ColdFusion site.

5.       Extension
We can extend CFML further by creating custom tags or user-defined functions (UDFs), or by integrating COM,C++, and Java objects by using CFX tag.

Q2. How coldfusion process the request?

1.   A web browser makes a request to a web server for a template with a .cfm extension.
2.   The web server receives the request and forwards it to the ColdFusion Application Server.
3.   The ColdFusion Application Server parses the CFML template and processes the tags and functions accordingly, interacting with other services, such as data sources or mail servers, directory, file servers, report servers etc.
4.   The ColdFusion Application Server combines its dynamic output with the static HTML (and JavaScript or VB Script, if any) in the template and passes the whole page back to the web server.
5.   The web server passes the dynamically generated content back to the client machine’s web browser.


Topic 3 – Application.cfm and Application.cfc

Q1. What is Application.cfm?

When ColdFusion receives a request for an application page, it searches the pages directory for a file named Application.cfm. If not exists, the Application.cfm code is logically included at the beginning of that application page.

If your application runs on a UNIX platform, which is case-sensitive, you must spell Application.cfm with an initial capital letter.

Q2. Can we have multiple “Application.cfm” file in an Application?

Yes. If several directories in the directory tree have an Application.cfm page, ColdFusion uses the first page it finds.

If the Application.cfm page is present in the directory tree (and has the required permissions set), you cannot prevent ColdFusion from including it.

ColdFusion processes only one Application.cfm page for each request.

If a ColdFusion page has a cfinclude tag pointing to an additional ColdFusion page, ColdFusion does not search for an Application.cfm page when it includes the additional page.

Q3. What are different events in Aplication.cfc?

We can implement following events through Application.cfc –
1. onApplicationStart:

The very first time your application is used, the onApplicationStart event is broadcast. This gives you an opportunity to define some application-specific configuration.

The important part to remember is that, as a rule of thumb, it only happens once, until your application times out the process is restarted, or the computer is restarted.

2.onSessionStart:

Any time that a user makes a request to your application and either they haven't used it before, or it's been long enough that their session has expired -- as identified by their cookies, usually -- the onSessionStartevent is broadcast.

This allows you to set session defaults, like a flag indicating that the user is not currently logged in; or to redirect to the login page.

3. onRequestStart:

onRequestStart is broadcast before every request, giving you an opportunity to set variables   that should be accessible on every page in the site, or to validate that the user is allowed access to the requested page, for instance.

4.onRequest:
onRequestStart is   broadcast before onRequest, but they operate a little differently.

5.onRequestEnd:

Similarly, to onRequestStart, onRequestEnd is broadcast after your template returns control to CF, giving you the opportunity to add code to every request after the requested template has executed.

6.onSessionEnd:

You can use this to do things like empty a shopping cart that was never paid for thus returning that reserved stock back to availability for other customers to buy.

7.onApplicationEnd:

This event is broadcast when your application times out or if ColdFusion is shutting down.

8.onError:

Lastly, there is an onError event broadcast in the event of an un-caught exception, including any you might manually throw.

Q4. What is difference between Application.cfm and Application.cfc?
application.cfc gives you more control over when code runs.

In an application.cfm file, all of the code in that file is processed at the start of every page request.

With application.cfc we will write code in different methods which will get fired on specific events.

Q5. What if we have both Application.cfc and Application.cfm present in the same folder?

Application.cfc will be given more priority, Application.cfm will be ignored if the ColdFusion version is ColdFusion MX 7 +.

If it is any version less that ColdFusion MX 7 then Application.cfm will be given more priority Application.cfc will be ignored because application.cfc was introduced in CF7.
References :

Q6. What is look up order for Application.cfc/Application.cfm in coldfusion?

We can set the order in which ColdFusion searches for Application.cfm or Application.cfc if it is not found in the current project folder.
 We can set ColdFusion to search as follows:
§  default search order: ColdFusion looks for an Application.cfc/Application.cfm file from the current folder until the system root directory. On Windows, this could be C:\ and on UNIX, /opt.

§  till web root: ColdFusion looks for an Application.cfc/Application.cfm file from the current folder till web root.

§  in web root: ColdFusion looks for an Application.cfc/Application.cfm file in the current folder or web root.

Topic 4 :  CFM and CFC

Q1 –What does CFC mean? How it is different from CFM page?
Cfc is more organized and tidy way of writing the coldfusion code.

Consider if we we writer few function udfs inside the cfm file then all that functions will get executed everytime we load the page ColdFusion components (otherwise known as CFCs) are a powerful feature of ColdFusion MX that allows developers to introduce object oriented programming techniques into their ColdFusion skillset.

A ColdFusion component is basically a collection of functions that relate to a given entity, like for example, a Customer. You could create a ColdFusion Component that is responsible for the programming logic regarding your customer records.

For example, you could create one ColdFusion component called customer.cfc that contains five functions to perform database queries. One could create a new customer record, another function could update customer records, another to retrieve, one for deleting, and one for listing your customers.
Other functions could be included too.

By doing this, you would have all your programming logic for customers in one place, which has got to be a good thing - you're effectively separating your presentation from your logic.

OK, so you're thinking, "I could have done that using a CFINCLUDE tag!". True, however, ColdFusion components are much more powerful than the CFINCLUDE tag.

Q2. What are the benefits of using ColdFusion Components?
  • Security: You can restrict access to a ColdFusion component and it's function
  • Performance: ColdFusion Components are faster. This is because they are compiled. Note that a ColdFusion component only has to be compilied the first time it is called. It will then be pre-compiled for all subesquent calls unless you update the component, in which case it will compile once again.
  • Extensibility: ColdFusion components can share methods with other ColdFusion components. You can also make them available to applications built in other languages by using SOAP or URL calls.
  • Reusability: You can code your component so that it is a "black box" in that you can move it around without anything breaking - it's a standalone piece of code that accepts input and provides output. Also, generally, once you've called a component in a page, you can reuse it without having to call it again in that page.
  • Documentation: ColdFusion Components are self documenting - they generate their own comments. This is based on the developer using the "Hint" attribute.
Q3. What are the different ways to invoke CFC?

Method 1:  <cfinvoke>
 <cfinvoke component="user" method="Get" returnvariable="usr">
 <cfinvokeargument name="id" value="#id#">
 </cfinvoke>

Method 2:

<cfobject component="user" name="userObj">
<cfinvoke component="#userObj#" method="Get" id="#id#" returnvariable="usr">

Method 3:
<cfscript>
 userObj=CreateObject("component", "user");
 user_id=userObj.Get(id);
 </cfscript>

Method 4: URL Invocation
When invoking CFCs via URLs, the method and any arguments are passed as URL parameters, as seen here:
http://localhost/users/user.cfc?method=get&id=1
Q4. What are the keywords or ways to impelement inheritance in the coldfsuion?

Extends attributes is used in coldfusion components to implements inheritance.

The Super keyword supports only one level of inheritance. If you use multiple levels of inheritance, you can only use the Super keyword to access the current component's immediate parent.

References:

Topic 5 – Custom Tags

Q1. What is custom tag in coldfusion?

CFML allows language extensions in the form of custom tags, which are tags created by the developer that are not part of the CFML language itself.

Custom tags are regular CFML files which are intended to be invoked as tags, although it is possible to treat a template as both a custom tag and a regular template.

Custom tags are written in CFML and are typically invoked by prefixing the custom tag's file name with cf_, although there are other ways to invoke custom tags.

If a template is invoked as a custom tag, the attributes used to invoke that tag are available within the tag in an attributes scope and the variables for the calling page are accessible via the caller scope.

For example, if writing a custom tag to perform addition, taking two attributes and adding them together, the tag would be an addition.cfm file which could look like this:

<cfset caller.addition = attributes.first + attributes.second />

Assuming the tag is in the same directory as the file or in a pre-defined customtags directory, it can be invoked thus:

<cf_addition first="1" second="2">

Custom tags can also be invoked by the CFMODULE  as follows-
<cfmodule first=”1” second=”2” template=”addition.cfm”>

References –

Q2. What are CFX tags?

CFX tags are custom tags which are developed using Java or C++, and are prefixed with cfx_ just like cf_. Java and C++ tags are added to the CFML runtime environment using the CFML engine's administrator or by editing configuration files.

Q3. What is use of cfmodule tag?

Invokes a custom tag for use in ColdFusion application pages.
Module.cfm
<cfset tempName = "Datta">
<cfmodule template="test.cfm"
                    firstname="dattatray"
          lastname="shinde">


Following cfm file will explain, how to call/use variables in caller file and passed parameters-

Test.cfm

<cfdump var="#caller.testName#">
<cfdump var="#attributes.firstName#">

If we have to use cfmodule tag with name=”test” parameter as follows then we need to keep test.cfm in C:\ColdFusion11\cfusion\CustomTags

<cfmodule name="test"
                    firstname="dattatray"
                    lastname="shinde">
               

Topic 6:  Coldfusion Scope Variables

Q1. What is Session scope?
session refers to all the connections that a single client might make to a server in the course of viewing any pages associated with a given application. Sessions are specific to both the individual user and the application. As a result, every user of an application has a separate session and has access to a separate set of session variables.

This logical view of a session begins with the first connection to an application by a client and ends after that client's last connection. However, because of the stateless nature of the web, it is not always possible to define a precise point at which a session ends. A session should end when the user finishes using an application. In most cases, however, a web application has no way of knowing if a user has finished or is just lingering over a page.

Therefore, sessions always terminate after a time-out period of inactivity. If the user does not access a page of the application within this time-out period, ColdFusion interprets this as the end of the session and clears any variables associated with that session.

The default time-out for session variables is 20 minutes. You can change the default time-out on the Memory Variables page in the Server Settings area in the ColdFusion Administrator. It is also possible to define session timeout time in Application.cfm or Application.cfc.

To uniquely identify user sessions CFID and CFTOKEN which are session variables will be used. Since some cases user might disable cookie, JSESSIONID can also be used to track sessions in coldfusion.

Reference :

Q2. What is client scope?
Client variables in coldfusion allows us to store user information and preference over the multiple session. Default timeout as known as purge interval for the client variables is 1 hr and 7 minits and cannot be less than 30 minuts.

Q3. What is Application Scope?
Application variables are available to all pages within an application, that is, pages that have the same application name. Because they are persistent, you can pass values between pages with a minimum of effort.
Unlike Client and Session variables, Application variables do not require that a client name (client ID) is associated with them. Thus, they are available to any clients that specify the same application name. Also, you do not need to use the cfapplication tag to enable Application variables.
Using the ColdFusion Administrator you can enable or disable Application variables in all applications; you cannot override this setting for an individual application.
Like Session variables, ColdFusion stores Application variables in the ColdFusion Server's memory and you can set timeout values for these variables either with cfapplication, or by specifying timeouts in the ColdFusion Administrator.


Q4. What is server Scope?
Server variables are associated with a single ColdFusion server. They are available to all applications that run on the server. Use server variables for data that must be accessed across clients and applications, such as global server hit counts.
Server variables do not time out, but they are lost when the server shuts down. We can delete server variables.

Server variables are stored on a single server. As a result, we should not use server variables if you use ColdFusion on a server cluster.
We access and manipulate server variables the same way use Session and application variables, except we use the variable prefix Server.

Server.ColdFusion.AppServer
The name of the J2EE application server ColdFusion is using. For ColdFusion server editions, which have an integrated application server, the name is JRun4.
Server.ColdFusion.Expiration
The date on which the ColdFusion license expires if it is the trial version.
Server.ColdFusion.ProductLevel
The server product level, such as Enterprise.
Server.ColdFusion.ProductName
The name of the product (ColdFusion).
Server.ColdFusion.ProductVersion
The version number for the server that is running, such as 6,0,0.
Server.ColdFusion.Rootdir
Directory under which ColdFusion is installed, such as C:\cfusion.
Server.ColdFusion.SerialNumber
The serial number assigned to this server installation.
Server.ColdFusion.SupportedLocales
The locales, such as English (US) and Spanish (Standard), supported by the server.
Server.OS.AdditionalInformation
Additional information provided by the operating system, such as the Service Pack number.
Server.OS.arch
The processor architecture, such as x86 for Intel Pentium processors.
Server.OS.BuildNumber
The specific operating system build, such as 1381
Server.OS.Name
The name of the operating system, such as Windows NT.
Server.OS.Version
   The version number of the operating system, such as 4.0.

Reference –

Q5. What are the differences between Client and Session Scope variables?
You can’t store complex structures inside the client variable but session can store complex structures.
Client variable by default will get stored in the registry but we can also store in database or in cookie. Session and Application variables will get stored in coldfusion server’s memory.

Q6. What are the default timeouts for the application and session variables?
Application – 2 days, Session- 20 mins
Application and session scopes are independent of each other. Application variables expire when you restart the ColdFusion server.

Session variables expire when the user's session ends. Both types of variables also expire after a time-out period that you specify on CFADMIN page or in the cfapplication tag. 
  • Server variables – tied to CF Server and Accessible by all clients and applications on a single Server
  • Application variables - Tied to a single application and accessible by multiple clients
  • Client variables - Tied to a single client and accessible over multiple sessions
  • Session variables – Tied to single user session and Exist for one client or browser during a single session
Q7. Can you delete all the session variables?
NO, The Session Client scope has four built-in, read-only variables –CFID, CFTOKEN, URLTOKEN, SESSIONID.


Topic 7: Error handling in coldfusion

Q1. What are different types of errors in coldfusion?

There are three types of ColdFusion Errors:
  1. Exception: Where the error stops the request from completing its process.
For example-
variable is not defined and used somewhere inside code
  1. Missing Template: When an HTTP request for a page cannot be found.
For example-
xyz.cfm used below doesnot exists.
<cfinclude template="xyz.cfm">
  1. Form Field Data Validation: When server side form validation fails.
For example-
credit card no validation as below.
<cfinput validate="creditcard" name="credit_card" id="credit_card" value="">


Q2. What are different ways to handle errors in coldfusion?

When an error is thrown, it will bubble up the application until the first Error Handler catches it. The order in which the handlers will be called is:
  1. CFCATCH
  2. CFERROR in Application.cfm OR onError() in Application.cfc
  3. Site-Wide error handling
  4. Coldfusion error handler
References –


Topic 8: Webservices in coldfusion

Q1. How to create and consume web service in coldfusion? SOAP based?

To Create a webservice in coldfusion all we need to do is create cfc first and write a function having acess as “remote”. That’s it.Coldfusion will automatically create a WSDL file for this webservice which can be viewed through browser (localhost:8500/Coldfusion/webservice/User.cfc?wsdl) or through coldfusion administrator (Data Services à web services)

<!---  User.cfc --->
<cfcomponent output="false">
                <cffunction access="remote" name="display_user" returntype="string">
                                <cfargument name="user" type="string">
                                <cfreturn "Hello" &  ' ' & user>
                </cffunction>
</cfcomponent>


The above created web service can be consumed in coldfusion as follow –

<!--- display_user.cfm --->
<cfinvoke  webservice="http://localhost:8500/coldfusion/webservice/user.cfc?wsdl"
                                method="display_user"
                    returnvariable="return_message" >
                                <cfinvokeargument  name="user" value="dattatray">
</cfinvoke>      
<cfoutput>
#return_message#
</cfoutput>

Reference –

Q2. How to create and consume REST based web service in coldfusion?

Topic 9 : Coldfusion Database Tags and Queries

Q1. What is the difference between CFQUERY and CFSTOREDPROC tags?
When should we use them?
Both the tags have their own context to use them.

CFQUERY tag is used to pass queries or SQL statements to a data source.
It is used to create dynamic queries.
cfqueryparam tag is used to validate parameters to avoid the SQL injection attack.

CFSTOREDPROC is used to execute stored procedure and cfprocparam to validate parameters but with
Cfprocresult tag can be used to accept multiple resultset return from database.

CFSTOREPROC will give the better performance whether it noticeable will be depends on your query and
Databse.

Q2. What is CFINSERT and CFUPDATE?
Inserts/Updates records in data sources from data in a ColdFusion form or form Scope.

Q3. What is CFDBINFO tag?
This tag retrieves information about a data source, including details about the database, tables, queries, procedures, foreign keys, indexes, and version information about the database, driver, and JDBC.

Q4. What is query of query in coldfusion?
A query that retrieves data from a record set is called a Query of Queries.You just need to mention dbtype = “query” in cfquery tag to do QoQ.

Topic 10: Object Relational Mapping ( ORM )   

Q1. What is ORM?
Relational databases are the core of most enterprise applications. However, when you map a relational database to objects, it becomes a challenge. Object relational mapping (ORM) is a programming framework that allows you to define a mapping between application object model and the relational database.
In an object model, the application objects are not aware of the database structure. Objects have properties and references to other objects. Databases consist of tables with columns that maybe related to other tables. ORM provides a bridge between the relational database and the object model.
By using ORM, you can access and update data entirely using the object model of an application. ORM provides features such as:
§  Database vendor independence
§  Caching
§  Concurrency
§  Performance optimization
§  Before ORM release in coldfusion 9, database access was achieved by:
§   Managing relational data using tags such as cfquery, cfinsert, and cfupdate, which handle SQL statements.
§  Managing objects using ColdFusion components (CFCs), and object lifecycle using the application itself
§  Writing SQL queries for each CFC, even for basic CRUD (Create, Retrieve, Update, and Delete) operations.
§  The complexity of managing these tasks increases as your application grows.
§  ColdFusion ORM automates most of these tasks, which:
§  Makes application code cleaner and more manageable
§  Enhances your productivity and lets you develop database applications faster
§  Creates applications that can run faster because of built-in ORM optimizations
§  Minimizes the amount of code you write
Apart from providing a framework for mapping the object model with the relational database, ColdFusionORM provides data query and retrieval facilities.


Topic 11: Coldfusion Mobile Applications
I have not created any questions on this topic but following links will help to understand the process of creation of mobile applications with coldfusion -
My Blog Post -
ColdFusion 11: My First Mobile Application (Hello World)
RAM'S BLOG


Topic 12 – Event Gateways in coldfusion

Q1. What are event gateways in coldfusion?
ColdFusion event gateways are ColdFusion elements that let ColdFusion react to or generate external events or messages in an asynchronous manner. 
Suppose we have sent 1000 emails of 1000 messages at one event like click or page submission, in this case it is not good practice to wait for event to complete. It will take hell lot of time. So in this type of scenario we can use Coldfusion event gateways which will complete the task asynchronously.

Topic 13: Coldfusion Application Frameworks

Q1. What is fusebox?

Fusebox is a framework for building web applications. It is meant to make your applications easier to create and maintain
A Fusebox application is made up of Circuits. A Circuit corresponds to a directory in your application.
Within each circuit are one or more Fuseactions. A Fuseaction is a request handler.
And finally, a Fuseaction does its work by executing one or more Fuses.
Fuses are individual CFML templates such as display files.
The framework uses XML configuration files to define the application settings as well as declaring what each Circuit does and how Fuseactions within each Circuit execute.
There is a core set of XML grammar that is used to create these files.
The framework is fully extensible via plugins.
Fusebox does not force the Model-View-Controller (MVC) pattern or Object-Oriented Programming (OOP) on the developer. However, either or both of these development approaches can be used with Fusebox.
Q2. What are some other application frameworks?
  • cfwheels - An open source ColdFusion framework inspired by Ruby on Rails.
  • ColdBox - The Enterprise ColdFusion MVC Development Platform
  • FarCry - FarCry Core is a web application framework that helps CFML developers build tailor-made content solutions, fast.
  • FW/1 - Framework One - a lightweight, convention over configuration, MVC application framework
  • ModelGlue - a CFML based, full stack, front controller based on MVC. Features include Scaffolding, ORM integration, and many others

Topic 14: Miscellaneous

Q1. Which is efficient isDefined() or structKeyExists()? Why?

These days (CF8+) the difference in speed is not that great. However, structKeyExists is indeed a little faster. Here's why.
When you use isDefined, the string you pass in is searched for as a key name in several scopes. As of CF9, the list of scopes.
1.    Local (function local, UDFs and CFCs only)
2.    Arguments
3.    Thread local (inside threads only)
4.    Query (not a true scope, applies for variables within query loops)
5.    Thread
6.    Variables
7.    CGI
8.    CFFile
9.    URL
10.  Form
11.  Cookie
12.  Client
Even if you use the scope name with isDefined (like: if isDefined('variables.foo')) the list will still be checked in order; and if the variable local.variables.foo is defined, it will be found BEFORE variables.foo.
On the other hand, structKeyExists only searches the structure you pass it for the existence of the key name; so there are far fewer places it will have to look.
By using more explicit code (structKeyExists), not only are you gaining some performance, but your code is more readable and maintainable, in my opinion.

Q2. What are CFFILE tag actions?
Manages interactions with server files. Following are the actions of the cffile tag:
§  Append
§  Copy
§  Delete
§  Move
§  Read
§  Readbinary
§  Rename
§  Upload
§  Uploadall
§  Write

Q3. What are the different actions in CFPDF tag?

Add a watermark to a PDF document
<cfpdf    action = "addwatermark">

Delete pages from a PDF document
<cfpdf  action = "deletepages">

Retrieve information about a PDF document
<cfpdf   action = "getinfo">

Merge PDF documents into an output PDF file
<cfpdf  action = "merge">

Set passwords and encrypt PDF documnets
<cfpdf action = "protect">
   
Remove a watermark from a PDF document
<cfpdf action = "removeWatermark">

Set information about a PDF document
<cfpdf action = "setinfo">

Write a PDF document to an output file
<cfpdf action = "write">


This list of Q & A, I have created with my experience of more than 10 years in coldfusion. I have taken more than 50 interviews throughout my carrier and opted more than that. However, if you feel that some different topics I should incorporate, please comment or write to me!

Please donate if you like my work!
Donate if you like my work

PS - This is the new page that I have created recently, so old comments are removed.



15 comments:

  1. Thank You Datta for preparing such a great questionnaire.

    ReplyDelete
  2. Thank You Datta, these topic are useful.

    ReplyDelete
  3. Its so much very helpful.. Thank you a lot...

    ReplyDelete
  4. Great post! Nice information keep sharing, Thank you. Enterprise Software Solutions

    ReplyDelete
  5. Thanks to Admin for Sharing such useful Information. I really like your Blog. Addition to your Story here I am Contributing 1 more Similar Story UI Developer Interview Questions for Experienced Professionals.

    ReplyDelete
  6. This comment has been removed by a blog administrator.

    ReplyDelete
  7. This comment has been removed by a blog administrator.

    ReplyDelete
  8. Happy to see Coldfusion is still actively supported. Worked on it almost 18 years back.

    ReplyDelete
  9. Thank you datta. this is helpful

    ReplyDelete
  10. thank you to the most importent question for explain

    ReplyDelete
  11. This comment has been removed by a blog administrator.

    ReplyDelete