Question 121: How much enterprise data does Gartner predict will be created and processed at the edge by 2025?
Correct Answer: C. 75%
In 2018, only 10% of an organization’s data was at the edge, according to Gartner senior research director Santhosh Rao, in the Gartner report “What Edge Computing Means for Infrastructure and Operations Leaders.” By 2025, Gartner estimated the number will grow to 75% of all enterprise data. The increase in data created at the edge will make transmitting the IoT data deluge to a cloud inefficient.
Question 122: Which is not a characteristic of headless CMS?
A. Cloud-friendly content management
B. Driven by RESTful APIs
C. Includes front-end content delivery
D. Used to create content for use across multiple channels
Correct Answer: C. Includes front-end content delivery
Headless CMS delivers back-end capabilities for editing, organizing and storing all types of digital information, without regard to how that content is published, displayed or used. Companies then choose separate front-end delivery tools, which enable them to publish content on a variety of channels, such as websites, apps, social media, kiosks and augmented reality displays. By not requiring a specified delivery environment, headless CMS separates the creative process of content production from the technical process of content delivery.
Question 123: Organizations generally use headless CMS architectures for what purpose?
A. Web content management
B. Enterprise content management
C. Content publication
D. Digital asset management
Correct Answer: A. Web content management
Most organizations use headless CMS for web content management (WCM). However, as companies create more digital experiences for employees, they may eventually use headless architectures for enterprise content management and digital asset management as well. Headless CMSes, by nature, need to be paired with a back-end content delivery system.
Question 124: Why might an organization not want to use headless CMS?
A. Less agile business operations
B. Requires developers to program APIs
C. Slow ROI
D. The organization publishes a lot of content.
Correct Answer: B. Requires developers to program APIs
As expert Geoffrey Bock wrote: “Headless CMS is not for the faint of heart.” While headless CMSes can handle a lot of content, deliver a faster ROI than traditional WCM systems (WCMSes) and enable more agile business operations, they also require a lot of in-house care. Application developers write APIs in order to deliver front-end experiences that meet business needs and are useful to end users.
Question 125: Which vendor does not have a headless CMS offering?
B. Drupal 8
D. Cloud CMS
Correct Answer: A. WordPress
WordPress is a classic example of a traditional CMS where content is produced, edited and saved through a back-end database and then published through a front-end delivery layer. Originally, Drupal was also a more traditional, open source CMS but began offering a headless option in Drupal 8. There is also a variety of natively headless CMSes on the market, such as Contentful, Cloud CMS, Built.io and Prismic.
Question 126: Headless CMSes cannot be integrated with traditional WCMSes.
Correct Answer: B. False
Some enterprises with existing web CMS foundations are tapping into new API sets from WCM providers, such as Hippo and SDL, to separate content production from content delivery. This is an example of microservices architecture, an approach to application development in which a large application is built as a suite of modular components or services.
Question 127: Which is a true statement about the differences between decoupled and headless CMS?
A. Decoupled CMS uses one server, while headless CMS uses two.
B. Decoupled CMS delivers content across multiple channels. Headless CMS delivers content on a single channel.
C. Decoupled CMS is less secure than headless CMS.
D. Decoupled CMS is less flexible than headless CMS.
Correct Answer: D. Decoupled CMS is less flexible than headless CMS.
Decoupled CMS is designed to deliver content for full-screen web. Like a traditional CMS, it includes both front-end and back-end services, but it separates these services onto two servers. It improves security and website performance but does not offer the flexible, multichannel content production options that headless CMS does.