Answer these 40 Atom (code editor) MCQs and see how sharp is your knowledge of Atom (code editor).
Scroll down and let's start!
A. atom:name
B. atom:uri
C. atom:email
D. atom:feed
A. The rel attribute contains the link's IRI whereas the href attribute indicates the link relation type.
B. The rel attribute is a required attribute whereas the href attribute is an optional attribute.
C. The value href attribute must be an IRI reference [RFC3987] whereas the value of the rel attribute may either match the isegment-nz-nc or the IRI reference.
D. None of the above
A. term
B. scheme
C. label
D. href
A. <atom:generator>
B. <atom:publisher>
C. <atom:author>
D. <atom:copyright>
A. True
B. False
A. <updated>
B. <source>
C. <category>
D. <title>
A. <atom:created>
B. <atom:issued>
C. <atom:modified>
D. <atom:updated>
A. Using a different hash key to decrypt an Atom Document
B. Changing the digital signatures of an Atom Document
C. Changing bits in a way that the decrypted message makes sense but has a different meaning
D. None of these
A. version
B. uri
C. term
D. label
A. The content of an atom:logo element is an Internationalized Resource Identifier (IRI) [RFC3987] where as the content of an atom:logo element is a Uniform Resource Identifier (URI) [RFC3986].
B. The atom:icon element identifies a small image and provides an iconic visual identification for the feed whereas the atom:logo element identifies a larger image and provides visual identification for the feed.
C. In case of an atom:logo element, the image must have an aspect ratio of one (horizontal) to one (vertical) whereas for an atom:icon element, the image must have an aspect ratio of 2 (horizontal) to 1 (vertical).
D. None of these
A. AES-128
B. AES-256
C. Blowfish
D. IDEA
E. TripleDES
A. Watermarking
B. Signing and Encryption
C. Digital Signatures
D. Hash Function
A. True
B. False
A. AES-128
B. AES-256
C. Blowfish
D. IDEA
A. Verifying the hash in the signature in the document
B. Comparing the decrypted Atom Document with the original Atom Document
C. Using message authentication code (MAC) authentication
D. Verifying a hash of the document within the document
A. Provide the scheme in uppercase characters.
B. Provide the host, if any, in lowercase characters.
C. Use uppercase A through H characters when percent-encoding.
D. For schemes that define an empty path to be equivalent to a path of "/", use "/".
E. For schemes that define a port, use an empty port if the default is desired.
A. text
B. html
C. xhtml
D. xml
A. <updated>2003-12-13t18:30:02Z</updated>
B. <updated>2003-12-13T18:30:02</updated>
C. <updated>2003-12-13T18:30:02.25+01:00</updated>
D. <updated>2003-12-13t18:30:02+01:00</updated>
A. The document must be encrypted first and then signed.
B. The document must be signed first and then encrypted.
C. Either of the above orders may be followed.
D. None of these
A. <link type="application/atom+xml" href="http://atom.com/atom.xml"/>
B. <link href="http://example.org/feed/" rel="self" />
C. <link href="atom.xml" type="application/atom+xml" rel="alternate" />
D. <link title="Atom Feed" href="http://atom.com/atom.xml"/>
A. URI
B. string
C. text
D. media type
A. URI
B. media type
C. string
D. binary data
A. Removing the atom:id element from the Atom Document
B. Adding an atom:id element to the Atom Document
C. Creating a duplicate of an Atom Document by publishing a falsified atom:source element
D. None of these
A. text
B. xml
C. html
D. base64
E. xhtml
A. atom:name
B. atom:feed
C. atom:uri
D. atom:email
A. Improper handling of the keying material used for Message Authentication Code (MAC) authentication may cause security risks for Atom Documents.
B. Message Authentication Code (MAC) does not ensure the integrity of Atom Documents.
C. Atom Documents do not support Message Authentication Code (MAC) for the Digital signature security mechanism.
D. Message Authentication Code (MAC) is not compatible with the Digital signature security mechanism used for Atom Documents.
A. atom:rights
B. atom:source
C. atom:published
D. atom:title
A. unique identifier
B. category
C. title
D. timestamp
A. Digital Signatures
B. Watermarking
C. Encryption
D. Message Integrity Code (MIC)
A. 1 and 2
B. 1 and 3
C. 4 and 5
D. 2 and 3
E. None of these
A. Rome
B. Apache Abdera
C. Apache POI
D. OpenJDK
A. term
B. scheme
C. label
D. All of the above
A. Atom 1.0 offers built-in support for XML Digital Signatures and XML Encryption.
B. Atom 1.0 is not in an XML namespace but may contain elements from other XML namespaces.
C. Atom 1.0 documents can be identified by a MIME media type.
D. Atom 1.0 includes a non-normative RELAX NG schema that validates Atom Document instances.
E. Atom 1.0 includes relative IRI support using xml:base.
A. Text construct
B. Person construct
C. Date construct
D. All of the above
A. title
B. href
C. rel
D. type
A. atom:published
B. atom:summary
C. atom:updated
D. atom:title
E. atom:rights
A. Person
B. Date
C. Content
D. Link
A. Counter (CTR)
B. Electronic codebook (ECB)
C. Output feedback (OFB)
D. Propagating cipher-block chaining (PCBC)
E. Cipher Block Chaining (CBC)
A. text
B. html
C. xml
D. xhtml
A. self
B. related
C. alternate
D. viaÂ
A. Watermarking
B. Encryption
C. Hash Function
D. Digital Signatures