Thanks Ronnie, Makes sense
Although maybe the Month and year when the show was released may be a way around that. So that it give us an indication of how current the shows is.
eg. for the AWS exams released in April 2018, the show whether it be recorded in december 2017 or March 2018 will have an release date of April 2018. Just a thought.
Also worth mentioning, If and when the objectives change perhaps it could be noted in the lecture notes at the bottom of the video any changes to the exam and any whitepapers the shows are based on. That way the membership can be assured that the information has been amended and referenced to it. That way the site is always relevant and as updated as it can be. Just another suggestion to make ITPRO.TV the best platform out there.
Congratulations on your pass, great job. The accelerated A+ is hard to pick out which of those episodes will be just focused on 901 or 902. Here is why, when we put those shows together we grouped the objective topics based on a their association together across both exams. So the easiest way would be to watch the whole show. I would recommend using other study methods as well, like books, flashcards, notes....etc. This will increase your chance of pass on 902. If you have any other questions please keep them coming!
AWS, Amazon Web Services, Cloud Services
I hope all is well. Mighty TALL order you have tasked me with here, let's see what we can do to whittle this down to a manageable size, shall we?
I will take them in the order that you asked them in:What are the forest and domain functional level requirements for each feature of AD FS? Ie.. Device registration, certificate authentication, etc...
Check out the following to get the Low-Down across the Feature set for ADFS:
AD DS requirements - This is where it gets CRAZZZZZZZZZZZZY ... :)
Domain controller requirements:
AD FS requires Domain controllers running Windows Server 2008 or later.
At least one Windows Server 2016 domain controller is required for Microsoft Passport for Work.
Domain functional-level requirements:
All user account domains and the domain to which the AD FS servers are joined must be operating at the domain functional level of Windows Server 2003 or higher.
A Windows Server 2008 domain functional level or higher is required for client certificate authentication if the certificate is explicitly mapped to a user's account in AD DS.
New installations of AD FS 2016 require the Active Directory 2016 schema (minimum version 85).
Raising the AD FS farm behavior level (FBL) to the 2016 level requires the Active Directory 2016 schema (minimum version 85).
Service account requirements:
Any standard domain account can be used as a service account for AD FS. Group Managed Service accounts are also supported. The permissions required at runtime will be added automatically when you configure AD FS.
Group Managed service accounts require at least one domain controller running Windows Server 2012 or higher. The GMSA must live under the default 'CN=Managed Service Accounts' container.
Sooooooo... what does all that actually mean?
Well several things actually, but take a look at the following as, it explains the FBL concept, versioning and how it all comes together:
If interested in what Server 2019 does to the mix, check out the following:
No. Although a little dated, the following gives you a good overview idea of the differences:
Hope that helps to put things in perspective and move you in the right direction(s).
Let me k now if you have any follow up questions.
I hope all is well.
You are stating that "there are different encrypted data outcomes for the same plain text with the same algorithm (3DES) and the same key"
While that is possible if the implementation parameters of the cryptosystem change, I am not sure how CryptoDemo implements the crypto functions that you are examining, and as a result, I am unsure whether or not that is expected behavior.
For instance, if you were to vary the Initialization Vector, if one were being used, then this behavior would be expected. If you were to implement 3DES using different modes, then the behavior may also be possible.
The short answer to your question is that if you kept EVERYTHING the same in the cryptosystem, then the same plaintext should always produce the same ciphertext, and vice versa, assuming that the same key pair is used for the system at all times.
The way that you get to the last part of your question statement, " So does that mean that there are infinite number of Crypto texts which could be decrypted to arrive at the same plain text? (assuming same 3DES algorithm and same key)" is that one or more elements of the cryptosystem must change in order to produce the different ciphertext outputs.
I hope that this helps to clarify.
Please let me know if I can answer any further questions.
IT Service Managment
If the are ISO 27001 then I would hope they would have network diagrams and plenty of documentation.
My starting point would be Network Diagrams, Server/Systems documentation and Security posture reports. If they are using monitoring tools, you might get a network diagram from this.